Feature Request: Support dynamic variables/inputs for nested components within a component
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Customer looking to leverage CI/CD catalog to improve efficiency in their monolithic project. Ideally, the customer will have a workflow component with multiple other components. The downstream project will inherit the workflow component. The customer does not want the downstream projects to inherit individual components to stop developers from cherry-picking which components to use and help standardise CI best practices across their organisation.
The ideal workflow is that the workflow component will contain the specs and the input variables and developers should be able to overwrite dynamic variables at the job level in the downstream project. There should be a flag at the spec level to say which variables to pass down or which to override.
- CI Component (Unit of Pipeline Configuration) --> Input spec defined for each unit of pipeline configuration - numerous CI components will be created at this level
- CI Component (Complete Pipeline Configuration) --> CI Component which aggregates the relevant CI Components (units of pipeline configuration) together to define a complete pipeline configuration - numerous CI components will be created at this level to cater for the various deployments we need to support.
- Downstream project pipeline --> Includes the relevant CI Component for the complete pipeline configuration and would set the dynamic input values declared for each unit of the pipeline configuration.
- CI Component (Complete Pipeline Configuration) --> CI Component which aggregates the relevant CI Components (units of pipeline configuration) together to define a complete pipeline configuration - numerous CI components will be created at this level to cater for the various deployments we need to support.
Intended users
Developers
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.
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.