Skip to content
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

Backport PR #16899 to 8.17: plugin manager: add --level=[major|minor|patch] (default: minor) #16974

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

github-actions[bot]
Copy link
Contributor

Backport PR #16899 to 8.17 branch, original message:


Release notes

  • By default, the plugin manager will no longer consume breaking changes in plugins, and will instead only consume minor revisions. If you wish to consume breaking changes, you must now explicitly add the --level=major flag.

What does this PR do?

Adds --level=[major|minor|patch] to the bin/logstash-plugin update command, with default value minor, 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

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files (and/or docker env variables)
  • I have added tests that prove my fix is effective or that my feature works

closes: #16894

…16899)

* plugin manager: add `--level=[major|minor|patch]` (default: `minor`)

* docs: plugin manager update `--level` behavior

* Update docs/static/plugin-manager.asciidoc

Co-authored-by: João Duarte <jsvd@users.noreply.github.com>

* docs: plugin update major as subheading

* docs: intention-first in major plugin updates

* Update docs/static/plugin-manager.asciidoc

Co-authored-by: Karen Metts <35154725+karenzone@users.noreply.github.com>

---------

Co-authored-by: João Duarte <jsvd@users.noreply.github.com>
Co-authored-by: Karen Metts <35154725+karenzone@users.noreply.github.com>
(cherry picked from commit 6943df5)
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

@yaauie yaauie merged commit 77e355e into 8.17 Jan 29, 2025
5 checks passed
@yaauie yaauie deleted the backport_16899_8.17 branch January 29, 2025 01:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants