Standardized behavior for kustomize edit

[koba1t]

Eschewed features

• This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

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,

• If the user uses any file path, that file does not exist.
• If the user adds the same one that already exists.
• If the user adds any literals that are already marked deprecated.

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

• I am interested in contributing this feature myself! 🎉

[k8s-ci-robot]

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 triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[stormqueen1990]

/remove-lifecycle stale
/lifecycle frozen