kustomize edit add doesn't support configurations

[danrollason-dd]

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?

Please add configurations as a section supported by kustomize edit add.

Why is this needed?

To enable adding configurations to a kustomization.yaml file programmatically.

Can you accomplish the motivating task without this feature, and if so, how?

Not easily

What other solutions have you considered?

echoing the content directly into the file but it would be inconsistent with all our other updates to the kustomization.yaml file.

Anything else we should know?

No response

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-sigs/prow repository.