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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 Fix crd flattening for structType marker to not create duplicate entries for XMapType #697
馃悰 Fix crd flattening for structType marker to not create duplicate entries for XMapType #697
Conversation
Bug was introduced in kubernetes-sigs#693.
cc @robbie-demuth : could you give this a try? |
/cherry-pick release-0.9 |
@sbueringer: once the present PR merges, I will cherry-pick it on top of release-0.9 in a new PR and assign it to you. 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. |
/lgtm |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, chrischdi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@sbueringer: #697 failed to apply on top of branch "release-0.9":
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. |
@chrischdi Can you please open a manual cherry-pick PR when you have some time? Thank you! |
Bug was introduced in #693.
As outlined in #693 (comment) , #693 introduced the bug that
x-kubernetes-map-type
may now get set twice and thus result in two entries inallOf
.This is because before #693 the marker at the type definition was simply ignored but now they got combined.
This PR fixes the flattening to handle this case for the
structType
marker.A similar fix for the markers
mapType
,listType
andlistMapKey
is not necessary because setting them where the type is referenced would result in an error anyway. Before #693 this was also the case, but since #693 it is possible to set them at the type definition.