Backport PR #15737 to 8.12: Fix logstash-keystore multiple keys operations with command flags #15739
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 #15737 to 8.12 branch, original message:
Release notes
[rn:skip]
What does this PR do?
Since
logstash-keystore
command supports multiple key (#15612), it has broken the following command in ECK aslogstash-keystore
takes--stdin
- and any other possible flag - as the second key, and not as a command option:This PR fixes how the keystore tool handle command's options, including validation for unknown options, and adding the
--stdin
flag to theadd
command.Why is it important/What is the impact to the user?
Checklist
How to test this PR locally
The following command should include a key named
FOO
with passwordFOO_PASSWORD
:Related issues