New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
operator-sdk/internal/generate: fix CSV path segments for multi-field structs #4166
operator-sdk/internal/generate: fix CSV path segments for multi-field structs #4166
Conversation
41b3f49
to
04c0136
Compare
internal/generate/clusterserviceversion/bases/definitions/ast.go
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after addressing nit
Co-authored-by: Eric Stroczynski <estroczy@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
Could we not add these markers in the samples?
@camilamacedo86 👍 to adding some spec and/or status descriptor markers to our samples, especially if we don't have to make any other major changes in the samples to support adding them. Can you make another issue to track this? |
/cherry-pick v1.1.x |
@joelanford: new pull request created: #4168 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
… structs (operator-framework#4166) Co-authored-by: Eric Stroczynski <estroczy@redhat.com> Signed-off-by: reinvantveer <rein.van.t.veer@geodan.nl>
Description of the change:
Fixes a bug that causes path segments to inadvertently re-use memory from other path segments, causing
specDescriptors
andstatusDescriptors
fields to end up with incorrect paths.Motivation for the change:
Fix bug = good :)
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments
(seechangelog/fragments/00-template.yaml
)website/content/en/docs