Skip to content

fix: Hierarchical overrides didn't handle removals#195

Open
rgibert wants to merge 2 commits into
mainfrom
rgibert/fix-hierarchical-include-removals
Open

fix: Hierarchical overrides didn't handle removals#195
rgibert wants to merge 2 commits into
mainfrom
rgibert/fix-hierarchical-include-removals

Conversation

@rgibert

@rgibert rgibert commented Jan 19, 2026

Copy link
Copy Markdown
Member

When using hierarchical overrides (e.g., single-tenant/_values.yaml → disney/default.yaml), setting a key to null would remove it from the intermediate merge result, but the deletion intent was lost. The key would then persist from the base service config because absent keys don't trigger any action during merges.

When using hierarchical overrides (e.g., single-tenant/_values.yaml → disney/default.yaml), setting a key to null would remove it from the intermediate merge result, but the deletion intent was lost. The key would then persist from the base service config because absent keys don't trigger any action during merges.
@rgibert rgibert self-assigned this Jan 19, 2026
@rgibert rgibert requested a review from a team as a code owner January 19, 2026 19:38
Comment thread libsentrykube/utils.py
@rgibert rgibert enabled auto-merge (squash) January 20, 2026 20:08
@rgibert rgibert disabled auto-merge January 20, 2026 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant