Exclude deployment tiers if a corresponding protected environment exist from creation form
requested to merge exclude-existing-deloyments-tiers-from-protected-environments-creation-form into master
What does this MR do and why?
This merge request excludes a deployment tier from the list in protected environments creation form (group-level), if a corresponding environment already is already protected. For example: if production
environment has already been protected then deployment tier production
won't show up in the list.
Resolves #364869 (closed).
Screenshots or screen recordings
Please see the screen recording below to see the fix in action.
How to set up and validate locally
To validate locally, follow the steps below:
- Create a group, and at least one subgroup underneath.
- Go to the parent group: Settings > CI/CD > Protected Environments.
- Protect one of the deployment tiers/environments, e.g.
production
. - Check the list of deployment tiers left, it should have excluded the one we just protected.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Ahmed Hemdan