Fix logging replacing secrets in values.yaml with (sensitive value)
#1611
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.
Description
There is currently a bug in the
logValues
function inhelm/resource_helm_release.go
which causes secrets in nested objects in the values map to get replaced with(sensitive value)
.To fix this I duplicated the logging code from
helm/data_helm_template.go
which uses json to do a deep clone of the object before replacing the secrets.Acceptance tests
Release Note
Release note for CHANGELOG:
References
Community Note