-
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
patch_namespaced_config_map merge-patch #968
Comments
This is a known issue. There is a PR proposing a fix: #959 |
/assign @roycaihw |
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. |
Stale issues rot after 30d 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. |
Closing this issue as a dup. Tracking the fix in #959 /close |
@roycaihw: Closing this issue. In response to this:
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. |
Description of the issue (please include outputs or screenshots if possible):
I am trying to patch a configmap that has two elements: roles and users.
I want to remove the element users from the configmap when the value is null. The default patch strategy appears to be a strategic merge, but I want to do a regular merge patch. How do you specify the merge strategy when you call the patch_namespaced_config_map() API? Do you have to use patch_namespaced_config_map_with_http_info? And if so, how do you pass the merge strategy to it?
The text was updated successfully, but these errors were encountered: