ACM-8739: ACM Policy that applies stringdata in a secret regression with templates #179
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: On second evaluation of a secret with stringData, the existingObject is modified while evaluating stringData for comparison. Since the order in which the keys are evaluated is varied, if the underlying object is modified first this may cause issues for future key evaluations.
Solution: when evaluating stringData, operate on a copy of the existing object's data so the actual object is not modified.
Ref: https://issues.redhat.com/browse/ACM-8739