Automatically update environments tier based on presence of deployment_tier in pipeline configuration

Problem to solve

Proposal

If a job creates an environment and no deployment_tier keyword is specified, that environment is assigned a tier based on the environment name. If a user then defines a deployment_tier for that job/environment later on, that value is ultimately ignored as the environment already exists with a tier definition.

This can be problematic for users who initially defined no deployment_tier for deployment jobs, but instead added these configurations later. For example, if a user is attempting to implement deployment control over protected environments, the behavior of who can execute these jobs can be inconsistent due to differing tiers assigned to these environments. As the user has no way of knowing what tier their environments have assigned (without using the API), one would expect a newly defined deployment_tier to be applied to an existing environment.

The presence of deployment_tier in the jobs environment configuration should update the tier of existing environments to avoid such confusions.

This behavior spurred this ticket impacting our Premium customer.

Intended users

• Priyanka (Platform Engineer)
• Rachel (Release Manager)
• Allison (Application Ops)
• Ingrid (Infrastructure Operator)

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.