Allow forked projects to access variables in the parent projects
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
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.
Problem to solve
Born from #11934 (closed)
Issue Allow fork pipelines to run in parent project allows users to run and access pipelines in the parent project (even if they are not project members)
However, they have no access to any variables in the parent project. Some customers may want to select some variables to be passed to such forked projects:
Forked projects cannot access
- Project/group-level variables
- Clusters
- Project/group-level specific runners,
- Environments/Deployments,
- Service Integrations, by default.
Optionally, the parent project can allow forked projects to access these resources by enabling additional checkboxes.
Intended users
Enterprise that uses forking workflow with GitLab
Proposal
Create additional setting under CI/CD to allow to pass on variables The variables can be selected - it shouldn't be all or nothing. The selected variables should be able to be used in the forked projects, pending that the setting is enabled. If disabled, forked projects should not be able to access the variables.