Backport PR #17039 to 8.18: Fix logstash-keystore to accept spaces in values when added via stdin #17040
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 PR #17039 to 8.18 branch, original message:
Release notes
Fix logstash-keystore to accept spaces in values when added via stdin
What does this PR do?
logstash-keystore
incorrectly handled values containing spaces, causing only the first word to be stored.For example, a value like "Hello, world!" was split, resulting in "Hello," as the stored value instead of the full string.
This commit preserves spaces in values, ensuring that multi-word strings are stored as intended.
Why is it important/What is the impact to the user?
This issue mainly affected ECK users who followed best practices for managing secure settings, leading to incorrect value assignments.
Users who use stdin to add value are impacted as well. For example,
echo "somevalue" | bin/logstash-keystore add hello
Checklist
Author's Checklist
How to test this PR locally
it should print "hello world"
Related issues
Use cases
Screenshots
Logs