use merge key list instead of a single merge key#3159
Conversation
|
Hi @natasha41575. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/assign @monopole |
fab35f3 to
bb5c79f
Compare
Shell32-Natsu
left a comment
There was a problem hiding this comment.
Please add a little bit more comments.
|
@natasha41575 Please add tests to Merge3 logic as well. This change affects both kpt and kustomize and we need tests to cover kpt(merge3) cases. |
3137492 to
cdfa1f6
Compare
|
/cc @monopole |
3fdb87c to
3c4014e
Compare
|
Please rebase and squash down to one commit. |
3c4014e to
e23efdb
Compare
e23efdb to
6788af0
Compare
monopole
left a comment
There was a problem hiding this comment.
yes, 2 commits better given two modules, thanks
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: monopole, natasha41575 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ref: #3111
Still a draft, but the test I added to patchstrategicmerge_test.go passes
Working on edge cases (will add tests) and cleaning up & removing some redundancy in the code
This will update kyaml to use x-kubernetes-list-map-keys from the OpenAPI schema as a merge key tuple.