feat(openpipeline-v2): add pipeline group resources #828
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
Kirdock
force-pushed
the
fix/openpipeline-v2/enum-values
branch
2 times, most recently
from
c821281 to
4ac9dfe
Compare
Kirdock
force-pushed
the
feat/openpipeline-add-pipeline-groups
branch
from
64a6213 to
b1e2363
Compare
Kirdock
force-pushed
the
feat/openpipeline-add-pipeline-groups
branch
from
b1e2363 to
3188a79
Compare
d0weinberger
previously approved these changes
Oct 22, 2025
Kirdock
force-pushed
the
feat/allow-feature-flags
branch
6 times, most recently
from
6e1c057 to
49a54f8
Compare
Kirdock
force-pushed
the
feat/openpipeline-add-pipeline-groups
branch
from
3188a79 to
0617b1c
Compare
This adds the pipeline-group resources for every openpipeline_v2 kind
This adds the pipeline groups to the provider and comments it out
Kirdock
force-pushed
the
feat/openpipeline-add-pipeline-groups
branch
from
0617b1c to
1a91df1
Compare
|
tomazpu
reviewed
Oct 30, 2025
| } | ||
| }, | ||
| "version": "1.21" | ||
| } No newline at end of file |
Collaborator
There was a problem hiding this comment.
new line missing at the end of file
Collaborator
Author
There was a problem hiding this comment.
I would say this is not really needed for JSON files (there won't be any additions below the object, as this would also lead to an invalid syntax), and because they're generated, I would prefer to either adjust it in the generator or leave it as it currently is :)
tomazpu
reviewed
Oct 30, 2025
tomazpu
approved these changes
Oct 30, 2025
d0weinberger
approved these changes
Oct 30, 2025
arthurpitman
approved these changes
Oct 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why this PR?
To support the upcoming openpipeline pipeline-groups schema
What has changed?
New pipeline-groups resources added for each kind
How does it do it?
Generating via schema
How is it tested?
Manual tests with one example locally. Tests will follow with E2E after this one is merged
How does it affect users?
It doesn't affect users at the moment, as it's not wired up yet. Still, once it is available, they will be able to use the pipeline-groups feature.
Issue: CA-16606