Enforce variables on child level to avoid overriding
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
To improve variable management at organizational level, there's no option today to stop a group variable from being overridden at the project or pipeline/job level. Users have to put together manual hacks to detect such overriding and make corrections.
Intended users
Development Team Leads, Platform Engineers, possible Release Managers
User experience goal
There should be convenient mechanisms in place to allow organisations to enforce and pass down variables to different teams.
Proposal
TBD--Add an setting to protect group variables from being overridden at a later stage.
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
Links / references
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.