Allow compliance pipelines to hold constant any values that are set from an include file
Release notes
Problem to solve
Compliance pipelines today hold constant any job or variables that are explicitly defined in them, regardless of ordering. This is great because it allows users to confidently set their configurations. When using include files though, the compliance framework does not enforce a first definition is final
sort of paradigm though, which can lead to confusion. Instead, users must correctly sequence the includes in the projects to ensure that the definitions get properly set.
Proposal
Allow users to specify in their compliance pipelines that a given include is intended to be final and that values that it defines cannot be overriden by subsequent included files.
Conceptual example:
include:
- file: myfile.yml
- allow_overrides: false # Don't allow values defined here to be overridden
Intended users
Feature Usage Metrics
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.