-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pluginmanager install preserve #17267
Conversation
This pull request does not have a backport label. Could you fix it @yaauie? 🙏
|
|
|
💚 Build Succeeded
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense, the test coverage is nice. Explicitly encoding in rspec what is happening with the behavior when not using --preserve
is helpful.
This pull request does not have a backport label. Could you fix it @yaauie? 🙏
|
|
* tests: integration tests for pluginmanager install --preserve * fix regression where pluginmanager's install --preserve flag didn't (cherry picked from commit a736178) # Conflicts: # qa/integration/specs/cli/install_spec.rb # qa/integration/specs/cli/pluginmanager_spec_helper.rb
* tests: integration tests for pluginmanager install --preserve * fix regression where pluginmanager's install --preserve flag didn't
* tests: integration tests for pluginmanager install --preserve * fix regression where pluginmanager's install --preserve flag didn't
* tests: integration tests for pluginmanager install --preserve * fix regression where pluginmanager's install --preserve flag didn't
* Pluginmanager clean after mutate (#17203) * pluginmanager: always clean after mutate * pluginmanager: don't skip updating plugins installed with --version * pr feedback (cherry picked from commit 8c96913) * Pluginmanager install preserve (#17267) * tests: integration tests for pluginmanager install --preserve * fix regression where pluginmanager's install --preserve flag didn't
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