Closed gabricc closed 1 year ago
The JSON patch mechanism we use is an IETF standard: https://datatracker.ietf.org/doc/html/rfc6902/. As such, its syntax and operations are not something that Kustomize should change.
/triage out-of-scope /close
@KnVerey: Closing this issue.
Eschewed features
What would you like to have added?
Hi everyone! It would be great if we could specify multiple paths in a single op, add/replace operation. Lot of times we have paths that require the same value, and we have to repeat it a lot of times.
Why is this needed?
This is an example where a lot of paths use the same
deployment-name
value. It makes the kustomization.yaml too repetitive:It would be great if we could do something like:
Can you accomplish the motivating task without this feature, and if so, how?
Yes, but the code gets too repetitive.
What other solutions have you considered?
I have considered using strategic merge patch, but it doesn’t fit so good to my scenario.
Anything else we should know?
Thanks!
Feature ownership