plugin manager: add --no-expand flag for list command#17124
Merged
yaauie merged 2 commits intoelastic:mainfrom Feb 27, 2025
Merged
plugin manager: add --no-expand flag for list command#17124yaauie merged 2 commits intoelastic:mainfrom
yaauie merged 2 commits intoelastic:mainfrom
Conversation
Allows us to avoid expanding aliases and integration plugins
2 tasks
This was referenced Feb 20, 2025
Member
Author
|
|
donoghuc
reviewed
Feb 20, 2025
|
💚 Build Succeeded
History
|
Member
Author
|
@logstashmachine backport 9.0 |
Member
Author
|
@logstashmachine backport 8.x |
github-actions bot
pushed a commit
that referenced
this pull request
Feb 27, 2025
* plugin manager: add --no-expand flag for list command Allows us to avoid expanding aliases and integration plugins * spec: escape expected output in regexp (cherry picked from commit 793e8c0)
4 tasks
github-actions bot
pushed a commit
that referenced
this pull request
Feb 27, 2025
* plugin manager: add --no-expand flag for list command Allows us to avoid expanding aliases and integration plugins * spec: escape expected output in regexp (cherry picked from commit 793e8c0)
4 tasks
yaauie
added a commit
that referenced
this pull request
Feb 27, 2025
* plugin manager: add --no-expand flag for list command Allows us to avoid expanding aliases and integration plugins * spec: escape expected output in regexp (cherry picked from commit 793e8c0) Co-authored-by: Ry Biesemeyer <yaauie@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Release notes
bin/logstash-plugin'slistcommand now supports a--no-expandflag to avoid expanding plugin aliases and the individual plugins within integration plugins.What does this PR do?
Adds
--[no-]expandflag (default: true) to the plugin manager'slistcommand, so that a caller can avoid expanding the integration plugins and aliases to get only a list of the plugin packages installed.Why is it important/What is the impact to the user?
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