Backport PR #13794 to 8.1: Feat: conservative plugin (dependency) updates by default #13803
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.
NOTE: do not merge until 8.1.0 is released, this will be part of 8.1.1
Backport PR #13794 to 8.1 branch, original message:
bin/logstash-plugin install logstash-input-s3-sns-sqs
New behavior (
--conservative
default) :Previous behavior (
--no-conservative
) :Release notes
The
bin/logstash-plugin
utility will, by default, behave more conservatively when updating plugin dependencies.What does this PR do?
Introduces
--conservative
(default) /--no-conservative
flag for plugin install and update.Why is it important/What is the impact to the user?
The user will end up less surprised when running
bin/logstash-plugin update
orinstall
(when dependencies such as a mixin needs an update to install the plugin).Checklist
How to test this PR locally
Run
bin/logstash-plugin install logstash-input-s3-sns-sqs
and compare the Gemfile.lock changes.Related issues
Pretty much avoids surprise updates of a dependency such as #13777