View group-level secret variables at project level
Description
We want to make users aware of all the variables that will be passed to their projects, even if they're group-level variables. At the moment the only way to see all the variables is to go to Settings > Pipelines for the project and then iterate on the same page for each group (and parent group) in order to have the full list.
Proposal
Let's make group-level variables available in all groups and projects that inherit them.
Example:
Let's consider the following path:
my-company-group / my-division-group / my-project
with the following secret variables:
- COMPANY_CONTACT (defined at my-company-group level)
- DIVISION_NAME (defined at my-division-group level)
- DEPLOYMENT_KEY (defined at my-project level)
We should see/edit 1
at my-company-group, see 1
and see/edit 2
at my-company-group level, see 1
, 2
and see/edit 3
at my-project level.
We can also consider to allow editing of group-level variables in the project scope, in that case they're "promoted" and a new project variable with the same name is added (and will take precedence over the group one).
Links / references
gitlab-ce#31218 gitlab-ce#12729
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