Revamp Environment states for better representation
Problem
This issue is for continuing the discussion raised by @vshushlin.
GitLab Environments has currently the following states:
-
available
... The environment is available for deployments, or is already live, or got a failed deployment, etc. This is the initial and default state. -
stopped
... The environment has been stopped. -
stopping
... This is a transient state betweenavailable
andstopped
. You can find more information in this issue.
The problem here is that the available
state is pretty ambiguous on its purpose. This subsequently causes a problem such as:
- When users visiting Environment index/detail pages, it's hard to understand whether the environment is empty, live or unknown state.
- It's hard to filter the environments by a scoped state. e.g. user wants to see only live environments. Related to #10754 (closed)
Proposal
Some ideas of environment statuses (from #241506[Iteration_3.png] (comment 1209546925)):
-
Healthy
🍏 -
Attention
⚠ -
Critical
🔴
Considerations:
- Should Deploy freeze be taken into account?
- Users can easily identify the root causes of the status. #375449[Deployment-Summary.png] (comment 1263537111). Likely creating an normal/incident issue from there and cross linking.
Edited by Shinya Maeda