Backport of Fix CLI panic caused by single backslash values into release/1.8.x #14737
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.
Backport
This PR is auto-generated from #14523 to be assessed for backporting due to the inclusion of the label backport/1.8.x.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
Passing
key=value
fields whose value is a single backslash to the CLI will cause a panic. The underlying cause exists ingo-secure-stdlib/kv-builder
. A fix has been introduced ingo-secure-stdlib/kv-builder
PR #35.This PR introduces the following changes:
go-secure-stdlib/kv-builder
tov0.1.2
Before change:
After change: