Backport PR #16899 to 8.17: plugin manager: add --level=[major|minor|patch]
(default: minor
)
#16974
+104
−9
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 #16899 to 8.17 branch, original message:
Release notes
--level=major
flag.What does this PR do?
Adds
--level=[major|minor|patch]
to thebin/logstash-plugin update
command, with default valueminor
, and propagates it to the underlying bundler's--major
,--minor
, or--patch
flags, to ensure users can upgrade while avoiding breaking changes.Why is it important/What is the impact to the user?
Users are currently being surprised when their
bin/logstash-plugin update
consumes breaking changes in plugins, causing their currently-valid pipeline configurations to fail to load. This removes the element of surprise, while still allowing users to upgrade across the major version of the plugins if they expressly wish to do so.Checklist
[ ] I have made corresponding change to the default configuration files (and/or docker env variables)closes: #16894