-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Standardized behavior for kustomize edit
#5563
Comments
This issue is currently awaiting triage. SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the The 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. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Eschewed features
What would you like to have added?
Make documentation of what is a common standardized behavior in all subcommands in the
kustomize edit
region to improve unified UX.Why is this needed?
Currently, the behavior of the
kustomize edit
subcommand is not standardized and documented and is sometimes confused when implemented to add a function for new literal support.I think we can decide to implement the same behavior at some points.
For example,
Can you accomplish the motivating task without this feature, and if so, how?
If we don't have this document, someone who wants to add support for the
edit
subcommand needs to check the already existing code for implementation, and the reviewer needs to check the behavior in that PR carefully.What other solutions have you considered?
I think none.
Anything else we should know?
So, we need to care about current implements in the
edit
subcommand behavior and keep the current behavior if we can.Feature ownership
The text was updated successfully, but these errors were encountered: