feat: support disabling components from pipelines #641
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@disrupted let me know if there is anything missing 🙏 |
to enable promotion through environments. simply adding the field `enabled: false` to a component definition will disable it in the generated pipeline. Example: ```yaml - type: components name: my-component enabled: false ```
to fix the tests
daconstenla
force-pushed
the
feat-support-disabling-components-from-pipelines
branch
from
411e1af to
4df00a3
Compare
disrupted
reviewed
Jan 29, 2026
tests/pipeline/resources/pipelines-with-graphs/simple-pipeline/pipeline_production.yaml
Show resolved
Hide resolved
disrupted
added
the
component/generator
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull-request introduces the flag
enabledto all pipeline components, by default istruewhich means default behavior is not changed, if set tofalsethen component is not part of any manifestation.This is particularly useful when there are pipelines for multiple environments and new components are introduced or old components are removed so they can be toggled on/off per-environment.
Relates to