Backport PR #17030 to 9.0: plugins: improve remove command to support multiple plugins
#17120
+349
−82
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removal works in a single pass by finding plugins that would have unmet
dependencies if all of the specified plugins were to be removed, and
proceeding with the removal only if no conflicts were created.
> ~~~
> ╭─{ rye@perhaps:~/src/elastic/logstash@main (pluginmanager-remove-multiple ✘) }
> ╰─● bin/logstash-plugin remove logstash-input-syslog logstash-filter-grok
> Using system java: /Users/rye/.jenv/shims/java
> Resolving dependencies......
> Successfully removed logstash-input-syslog
> Successfully removed logstash-filter-grok
> [success (00:00:05)]
~~~
(cherry picked from commit 0895588)
|
💚 Build Succeeded
|
andsel
added a commit
that referenced
this pull request
Mar 10, 2025
andsel
added a commit
that referenced
this pull request
Apr 7, 2025
* Update release notes for 8.18.0 * Refined release notes * Updated plugins section after Nokogiri update * Updated release docs after backport of #17185 * Re-added plugins section for 8.18.0 * Update after backport of #17120 * Update release notes with plugin changes * Update release notes with recent changes * Update docs/static/releasenotes.asciidoc Co-authored-by: Karen Metts <[email protected]> * Removed duplicated PR description Co-authored-by: Karen Metts <[email protected]> * Moved JDK update section before the plugin section --------- Co-authored-by: logstashmachine <[email protected]> Co-authored-by: andsel <[email protected]> Co-authored-by: Karen Metts <[email protected]>
mergify bot
pushed a commit
that referenced
this pull request
Apr 15, 2025
* Update release notes for 8.18.0 * Refined release notes * Updated plugins section after Nokogiri update * Updated release docs after backport of #17185 * Re-added plugins section for 8.18.0 * Update after backport of #17120 * Update release notes with plugin changes * Update release notes with recent changes * Update docs/static/releasenotes.asciidoc Co-authored-by: Karen Metts <[email protected]> * Removed duplicated PR description Co-authored-by: Karen Metts <[email protected]> * Moved JDK update section before the plugin section --------- Co-authored-by: logstashmachine <[email protected]> Co-authored-by: andsel <[email protected]> Co-authored-by: Karen Metts <[email protected]> (cherry picked from commit 5a66afa)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #17030 to 9.0 branch, original message:
Release notes
The plugin manager
bin/logstash-plugin'sremovecommand now allows multiple plugins to be removed in a single call. This simplifies removing plugins that depend on other plugins, so that the caller no longer needs to perform the removals in dependency order.What does this PR do?
Removal works by optimistically removing all specified plugin-gems from a mutable gemspec, then validating that doing so does not leave plugin-gems with orphaned runtime dependencies, saving the result and succeeding only if no conflicts were created.
Why is it important/What is the impact to the user?
Because the plugin manager (rightly) refuses to remove plugins that are depended on by other plugins and the plugin manager has historically only allowed one plugin to be removed at a time, the caller removing many plugins has needed to be aware of dependency order.
By allowing a list of plugins to be provided, the plugin manager is able to remove the requirement for dependency-order, and is able to handle the removals in a single execution.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs