Skip to content
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

Kubernetes Config file "deleteBeforeReplace" option #2221

Open
caboog opened this issue Oct 31, 2022 · 2 comments
Open

Kubernetes Config file "deleteBeforeReplace" option #2221

caboog opened this issue Oct 31, 2022 · 2 comments
Labels
area/yaml customer/feedback Feedback from customers kind/enhancement Improvements or new features mro2 Monica's list of 2st tier overlay related issues

Comments

@caboog
Copy link

caboog commented Oct 31, 2022

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Add a "deleteBeforeReplace" option for config files. https://www.pulumi.com/registry/packages/kubernetes/api-docs/yaml/configfile/#configfile

Affected area/feature

@caboog caboog added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Oct 31, 2022
@viveklak viveklak removed the needs-triage Needs attention from the triage team label Nov 2, 2022
@viveklak
Copy link
Contributor

viveklak commented Nov 2, 2022

Thanks for opening the issue @caboog. I have added this to our backlog and the team will look to prioritize it.

@mnlumi mnlumi added the mro2 Monica's list of 2st tier overlay related issues label Mar 28, 2023
@mnlumi mnlumi added the customer/feedback Feedback from customers label Oct 19, 2023
@EronWright
Copy link
Contributor

EronWright commented Mar 29, 2024

I interpret this feature request as, provide a way to set the deleteBeforeReplace option on the child resources. I imagine that you'd want to apply this to a specific child, not to all children. I would suggest that the user use the transform option to adjust the options on the child resource(s). An alternative would be to support an annotation, similar to skipAwait, to same effect.

Another interpretation would be a desire to delete all resources of a given ConfigFile eagerly when the ConfigFile is deleted or replaced. Today the resources are deleted lazily, and this can cause problems, e.g in migration cases. I'll assume this latter interpretation is not intended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/yaml customer/feedback Feedback from customers kind/enhancement Improvements or new features mro2 Monica's list of 2st tier overlay related issues
Projects
None yet
Development

No branches or pull requests

4 participants