fix: restore using latest secret state #69
Merged
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.
These changes are fixing the problem with original object being left mutated after restore execution. It was happening after more than one usage of redact function.
Compiled restore function now always pointing to the latest "secret" state.
Fixed test "does not increment secret size". Previously it was always testing the origin "secret" object, not the restored one, so in general generating false positive.
Extended test: "restores multi nested wildcard values" to cover multiple redact-restore executions.