-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Use separate search prefix for gems and additional plugin path #1133
Conversation
9cc919c
to
bc2d257
Compare
With this change, Fluentd seems to load all |
No. It's not intentional. Thanks for mention it. It seems to we need two rule of plugin search prefix.
|
This is working as we expect. but not looks good to me. |
Current your implementation is breaking code compatibility of |
My idea is to add optional keyword argument (like |
@tagomoris How about this one? HatsuneMiku3939@d57576a |
@HatsuneMiku3939 it looks good to me! |
4df9494
to
d57576a
Compare
@tagomoris |
LGTM |
Allow to search plugin from multiple prefix directory.
Related with issue #1131 (v0.14 doesn't load plugins from directory specified by "-p" option)