This repository was archived by the owner on Nov 1, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix values merge in helm-operator.
Values merges in
helm-operator
will overwrite instead of merge a dict that has it's keysdefined in more than two sources (e.g : Values and multiple ValuesFrom).
This happens because when merging,
flux/integrations/helm/release/release.go
Lines 507 to 514 in 6077df2
first iteration makes
dest[k]
achartutil.Values
and then at the next iteration will seeisMap
evaluate to False, overwriting instead of merging the two maps.I wrote a unit test that feed Values from a HelmRelease, a Configmap and a
Secret to make sure it fails, then changed
mergValues
signature to make it pass.After the signature change :
Fixes #1696.