-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 localize command handle #4959
Add localize command handle #4959
Conversation
/cc @yuwenma |
259374b
to
b54bbff
Compare
@natasha41575 Does the failed presubmit test: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kustomize/4959/kustomize-presubmit-master/1611155994727944192 mean that we need to release a new version of |
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.
/hold
We should make sure we have everything we want to add to alpha kustomize localize
before we expose it in the CLI.
Defer to @natasha41575 comments about some user messages and stylish suggestions, otherwise looks good on my side. 👍 |
@annasong20 I think you may have to split this PR into two parts, having the |
@yuwenma excellent suggestion! #4974 now handles the |
b54bbff
to
6111959
Compare
@annasong20: This PR has multiple commits, and the default merge method is: merge. 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. |
6111959
to
e278cbb
Compare
/label tide/merge-method-squash |
@natasha41575, @yuwenma, @KnVerey I cherry-picked the relevant commits from #4974, #4975 to demonstrate what the final code would look like. However, we should look at those 2 PRs first. After/If those PRs merge, I will rebase this one off master. |
e278cbb
to
b801bff
Compare
b801bff
to
b407d85
Compare
b407d85
to
9c47605
Compare
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.
I built off this branch and played around with kustomize localize
and it's looking good. I think one thing could be improved about the UX is I would like to see some sort of success message after running kustomize localize
. In particular, if I don't provide the destination argument, it would serve as an easy place for the user to see the name of the localized directory. Even if I do provide the destination argument, it's good feedback for the user to see that everything went as expected.
e.g. it would be nice to see
$ kustomize localize remote
Successfully localized `remote` into directory `localized-remote`.
Other than this small comment, this PR LGTM. I know we are waiting on #4975, so I can remove the hold on this when that goes in.
Thanks, @natasha41575! I exposed the destination directory path in #5010. Once that merges, I'll rebase and use the returned destination in the |
9c47605
to
4890e99
Compare
@natasha41575 I added the success message and rebased to include #5011, the merged solution to #4975. Lmk if there's anything else blocking this PR. |
/lgtm /hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: annasong20, natasha41575 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 |
This PR implements the handle that exposes
localize
as a command to users.In order to test the command handle code, this PR moves existing test helpers in
krusty
toapi/testutils
.