Skip to content

Fix duplicate key issue when using configmap config target #2584

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

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

ThoreKr
Copy link
Contributor

@ThoreKr ThoreKr commented Mar 15, 2024

When using the configTarget: "ConfigMap" option, the rendered configmap fails to install due to

  line 52: mapping key "persistent_volume_claim_retention_policy" already defined at line 51

This is caused by the flatten helper adding the config option too early causing duplicate keys like these to be created:

  persistent_volume_claim_retention_policy: "when_deleted:retain"
  persistent_volume_claim_retention_policy: "when_deleted:retain,when_scaled:retain"

This pr fixes this issue.

@FxKu
Copy link
Member

FxKu commented Mar 18, 2024

👍

@FxKu FxKu added this to the 1.11.0 milestone Mar 18, 2024
@idanovinda
Copy link
Member

👍

@FxKu
Copy link
Member

FxKu commented Mar 18, 2024

Thanks @ThoreKr . I will update the helm chart shortly after.

@FxKu FxKu merged commit 4cd4bee into zalando:master Mar 18, 2024
FxKu added a commit that referenced this pull request Mar 18, 2024
FxKu added a commit that referenced this pull request Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants