-
-
Notifications
You must be signed in to change notification settings - Fork 97
Load "all" plugins by default & allow "empty" values #2689
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
Conversation
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.
Just one minor comment. Thanks for tackling this one; I'll leave the remaining review to the team.
This is makes the OOTB experience so much better! |
08a12cf
to
02645f3
Compare
599148f
to
8850239
Compare
@tobim can I ask you to take the review from here on out? |
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 tested this change locally and all my calls to vast start and other sub commands behaved as expected.
Ready to be merged once the code change request is addressed.
…o anonymous namespace" This reverts commit 8850239.
e9938fa
to
c30abf5
Compare
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.
This is great, just some smaller things left to do. I also added a blocked
label to prevent this from being merged accidentally in the feature freeze for v2.4; whether this gets in regardless is up to @lava.
changelog/unreleased/changes/2689--load-all-plugins-by-default.md
Outdated
Show resolved
Hide resolved
Since the first rc will be tagged rc2 anyways we decided to squeeze this in in today's standup. |
This is a code base cleanup related to #2689. Historically speaking, "native plugins" were functionality that was part of libvast but used the plugin API. This allowed us to have defaults that we ship as built-in functionality. The only reason why we did not name them builtins from the get-go was because the term builtin was too close to the term bundled, which we already used for plugins that were built alongside VAST in the same build configuration (via `-DVAST_PLUGINS=...`). Now that bundled plugins are a purely internal term we can instead start referring to native plugins as builtins. In addition, this changes the show command to be a built-in instead without making any functional changes to it.
Load "all" plugins if no "plugins" configuration key is defined in the configuration.
📝 Reviewer Checklist
Review this pull request by ensuring the following items: