-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Add kubectl apply edit-last-applied
subcommand
#42256
Conversation
Hi @shiywang. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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. I understand the commands that are listed here. |
@kubernetes/sig-cli-feature-requests |
kubectl apply edit-last-applied
subcommandkubectl apply edit-last-applied
subcommand
@pwittrock @adohe also add some unit tests, ptal |
@k8s-bot ok to test |
@shiywang : can you please see the broken tests? |
6a922a4
to
fbebba8
Compare
@dims sure, done |
@pwittrock @adohe @ymqytw @kubernetes/sig-cli-feature-requests Can one of you please chime in? |
/assign @ymqytw |
/unassign @dims |
According to kubectl convention
I will revisit this tomorrow. |
/release-note |
@alexandercampbell thanks for you comments
I think current is fine, this command is almost same as
if not, return
used in function
there's only one last-applied-configuration object per objects |
InfoList []*resource.Info | ||
Mapper meta.RESTMapper | ||
Typer runtime.ObjectTyper | ||
ApplyPatchTypeList []types.PatchType |
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.
prefer a list of structs containing the patch content and patch type over parallel lists:
PatchBufferList []PatchBuffer
...
type PatchBuffer struct {
Patch []byte
PatchType types.PatchType
}
@k8s-bot pull-kubernetes-federation-e2e-gce test this |
@liggitt updated, not sure why pull-kubernetes-federation-e2e-gce always failed, ptal |
LGTM |
Thanks for your review. |
@k8s-bot pull-kubernetes-federation-e2e-gce test this |
# Edit the last-applied-configuration annotations by type/name in YAML. | ||
kubectl apply edit-last-applied deployment/nginx | ||
|
||
# Edit the last-applied-configuration annotations by file in JSON |
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.
The comment above at line 55 is punctuated, but this comment is not.
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.
oh, nice catch
only add a punctuation |
/lgtm |
@shiywang: you cannot LGTM your own PR. 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. I understand the commands that are listed here. |
/lgtm |
/approve |
1 similar comment
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, mengqiy, pwittrock, shiywang
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 42256, 46479, 45436, 46440, 46417) |
third command of kubernetes/community#287
Fixes #44905
@pwittrock @adohe @ymqytw @kubernetes/sig-cli-feature-requests could you guys have an early review ? cause some of feature I'm not sure about, will add unit tests if you think it's ok.