fix: update CodebaseBranch pipelines example with security field (#254) #256
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
The kubebuilder example annotation for the Pipelines field in CodebaseBranchSpec was missing the security pipeline configuration. This update adds the security field to the example, ensuring the generated CRD documentation accurately reflects all available pipeline types (build, review, and security) that users can configure. This aligns the Go source annotation with the CRD definition and ensures future `make manifests` runs will correctly preserve this field. Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
zmotso
approved these changes
Jan 21, 2026
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.
The kubebuilder example annotation for the Pipelines field in
CodebaseBranchSpec was missing the security pipeline configuration.
This update adds the security field to the example, ensuring the
generated CRD documentation accurately reflects all available pipeline
types (build, review, and security) that users can configure.
This aligns the Go source annotation with the CRD definition and ensures
future
make manifestsruns will correctly preserve this field.Fixes #254