[8.x] Pluginmanager install preserve (backport #17267) #17268
Closed
+241
−1
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.
Release notes
[rn:skip]
What does this PR do?
Fixes a regression introduced in #17203 that caused the
bin/logstash-plugin install --preserve
flag to not preserve.Why is it important/What is the impact to the user?
--version
, theGemfile
is amended to add the plugin and its version requirement.--preserve
flag should preserve the requirement.--version
to be upgraded had the side-effect of making the install command's--preserve
not work.Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)How to test this PR locally
This PR comes with tests and a fix separately. The tests can be used to verify the pre-broken behaviour as so:
back-out the portion of the breaking commit
This is an automatic backport of pull request #17267 done by [Mergify](https://mergify.com).