Skip to content

patch_namespaced_config_map merge-patch #968

Closed

Description

@jicowan

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.

roles: |
   - some values
users: |
   - some values

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?

Activity

  1. roycaihw commented on Oct 1, 2019

    @roycaihw
    Member

    This is a known issue. There is a PR proposing a fix: #959

  2. yliaog commented on Oct 8, 2019

    @yliaog
    Contributor

    /assign @roycaihw

  3. fejta-bot commented on Jan 6, 2020

    @fejta-bot

    Issues go stale after 90d of inactivity.
    Mark the issue as fresh with /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle stale

  4. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jan 6, 2020
  5. fejta-bot commented on Feb 5, 2020

    @fejta-bot

    Stale issues rot after 30d of inactivity.
    Mark the issue as fresh with /remove-lifecycle rotten.
    Rotten issues close after an additional 30d of inactivity.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle rotten

  6. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 5, 2020
  7. roycaihw commented on Feb 11, 2020

    @roycaihw
    Member

    Closing this issue as a dup. Tracking the fix in #959

    /close

  8. k8s-ci-robot commented on Feb 11, 2020

    @k8s-ci-robot
    Contributor

    @roycaihw: Closing this issue.

    Details

    In response to this:

    Closing this issue as a dup. Tracking the fix in #959

    /close

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/documentationCategorizes issue or PR as related to documentation.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions