-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
delete_from_yaml #940
Comments
/cc |
I can see this being added mimicking cc @micw523 |
k. I may think about refactoring the yaml utility too since we have the dynamic client now |
/assign |
Is there any progress? |
I'm also wondering if there will be some progress. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Hello, |
This would be a very helpful feature , I could use something like this in my project |
Bumping since this would be a great feature to have. It looks like the Apache Airflow K8s provider module has the described function implemented but it'd probably be better if the functionality was entirely in the kubernetes-client Python module. |
…l by DiptoChakrabarty) and update to latest Revive PR kubernetes-client#1392: Implement delete_from_yaml, solves kubernetes-client#940 (original by DiptoChakrabarty) and update to latest
…date to latest (original by DiptoChakrabarty) - Implement delete_from_yaml functionality - Combine create_from_yaml and delete_from_yaml into yaml_processor, preserving existing signatures for create
…date to latest (original by @DiptoChakrabarty) - Implement delete_from_yaml functionality - Combine create_from_yaml and delete_from_yaml into yaml_processor, preserving existing signatures for create
What is the feature and why do you need it:
Describe the solution you'd like to see:
Similar to the utils.create_from_yaml I would like to also have a delete_from_yaml function deleting all resources described in a yaml manifest.
The text was updated successfully, but these errors were encountered: