-
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
[Feature request] Replacements value in the structured data. #4517
Comments
@koba1t: 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. |
my implement is here(#4518) |
Thank you @koba1t for the feature request and the implementation. We have discussed this in the kustomize bug scrub, and while we leaning towards accepting some version of this feature, we noted that similar issue was filed for patches #3787. This has a long discussion of what this could look like for patches, and if we want to do something similar for replacements we believe they should have a similar UX. Because this is a major feature, this would need to be submitted as a mini in-repo KEP for further discussion, so that we can be very clear about what we are supporting. In that KEP, we should discuss the UX for both patches and replacements. Please let us know if you have any questions about the process. /triage under-consideration |
I tried to write a This is my first proposal, Could you give me any feedback? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
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 |
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 |
/triage accepted @koba1t I think we are inclined to accept the feature, we just need to take some time to get your KEP through. I'll see if I can find time to look at it again next week. |
Sending an update here that the KEP is merged, so please feel free to begin implementation. |
Thanks, Natasha! |
@koba1t any updates? |
This is a very cool feature. It would be really helpful for managing Kuberay configurations. Looking forward to it. |
@natasha41575, @koba1t any updates on this? This is much needed to fully embrace replacements. |
Hi @undr-rowr |
Is your feature request related to a problem? Please describe.
I feel difficult to Overlay when structured data is in k8s YAML's value. (ex. Structured data(yaml or json) format value in configMap data And structured data(almost json) format value in annotations(this way is used in many projects, I think)).
Therefore I propose to add options for replacing the value in structured data to replacements function.
I think this function can be an alternative vars function on almost use cases.
Example (json format value in configMap data)
Example (json format value in annotations)
Describe the solution you'd like
FIrst, set
format
andformatPath
parameters to replacements option.And interpretation in k8s YAML value using
formatPath
withformat
.Finally, execute replacements which place set by
formatPath
.(Please watch
Proposal config
on the "Additional context" section.)Describe alternatives you've considered
I tried to use
delimiter: '"'
options on replacement to parse json.I think I will be able to resolve my problem with this solution, but It is very hard.
Additional context
Proposal config
source
replacement
expected
The text was updated successfully, but these errors were encountered: