-
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
plugin manager: add --level=[major|minor|patch]
(default: minor
)
#16899
base: main
Are you sure you want to change the base?
Conversation
Confirmed it works correctly: Vanilla 8.17.0 `bin/logstash-plugin update`
Patched v8.17.0 `bin/logstash-plugin update`
We can see in the second no major versions were upgraded. |
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.
I've confirmed the behavior works as expected, just missing docs in https://github.com/elastic/logstash/blob/main/docs/static/plugin-manager.asciidoc?plain=1#L102-L113
📃 DOCS PREVIEW ✨ https://logstash_bk_16899.docs-preview.app.elstc.co/diff |
@@ -112,6 +112,21 @@ bin/logstash-plugin update logstash-input-github <2> | |||
<1> updates all installed plugins | |||
<2> updates only the plugin you specify | |||
|
|||
[NOTE] |
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.
I added this as an admonition because in the normal case users shouldn't need to concern themselves with this and will be happy to get the latest fully-compatible version available. It is rare that a user would want to jump across major versions of a plugin because we are taking care to backport non-breaking features and fixes to the previous minor.
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.
Doc nitpick, otherwise LGTM
Co-authored-by: João Duarte <[email protected]>
Quality Gate passedIssues Measures |
💚 Build Succeeded
History
cc @yaauie |
📃 DOCS PREVIEW ✨ https://logstash_bk_16899.docs-preview.app.elstc.co/diff |
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 changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)closes: #16894