glycam.org Status page missing useful metadata #117
Description
Tool:
https://glycam.org/status/versions/ is missing useful metadata we have
Bug Description:
I was kind of hoping to avoid doing a larger report, but since I am already kinda redoing this due to not being precise with my language, it is the perfect time to just go over everything.
- Improve given naming to be more useful
- For each of the fields that take the form of
*_GIT_BRANCH, the accompanying field will always sayactualthis can be useful to make sure we are always following our deployment pattern where only commits(/branches <-?) with that tag(/name <-?) are spun up. But having the codename tag (i.e.wistful-walker) for each bit of the stack will be easier for the brain. Yes, can copy past hash or enter in the first couple bits of hash but having the actual codename for each part of our deployment can be easier. Plus, they are cool names so why not have them here where we get our code metadata? It will also be nice for another more human way to check our test site vs our actual site. Finally ingemsandgmml, by having the codename tag listed, we can more cleanly get to the interesting commit; now going toactualin those repos takes you to the commit of theactualbranch not the repo we would make changes in, overall just smoother but yes I know I'm a little zany but it is logically nicer. - If we always want the
*_GIT_BRANCH:fields to sayactual, I would say we don't even have to display these fields if they are all actual as expected, and then have a dynamic warning message in red pop-up on the top of the status page saying something along the lines ofDeployment pattern where all parts should be actual brokenand then we display all of the fields that should always beactual. This is a nitpick, and I am a monkey with making UI/pretty things, so I can really only express how we just need to see the fields that should always sayactualif something is different than what we expect and defer to others for exact implementation so it doesn't look like a c++ dev made it lol.
- For each of the fields that take the form of
To Reproduce:
go to https://glycam.org/status/versions/
In gitkraken, open up the tags option in gems or gmml and try out using the codename tags of the deployments instead of using the actual branch as your marker. Unsure how to say this better, will be more observant of my workflow to better explain in future.
Expected behavior
Have the ability to see what is the codename tag that was deployed, and only see the fields that should always be actual if we need to see em aka they're not actual