Version control for project and group variables
Description
Using project and group variables to control or influence CI/CD pipelines is great, but configuration-as-code has some good benefits, such as being able to review and track changes, and rollback to prior values. We should think about how to add version control for these variables.
One way would be to put the variables in an external project and then read them into the primary project. This may be functional, but is pretty painful.
Another way would be to make a parallel repo associated with the project (https://gitlab.com/gitlab-org/gitlab-ce/issues/32374).
But maybe we could put a UI on something that happens to be backed by git, but isn't exposed as a repo.
Related: Changing values could automatically trigger redeploys or even rebuilds that depend on those values.
Proposal
Links / references
Documentation blurb
Overview
What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?
Use cases
Who is this for? Provide one or more use cases.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml