-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Add support for loading plugins from extra directories #13447
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
base: main
Are you sure you want to change the base?
Conversation
lynxplay
left a comment
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.
Right now, this automatically creates all specified directories, which is pretty annoying for what it is.
Could we alternatively create a secondary instance of the DirectoryProviderSource that is configured to not construct the directories it is preparing?
Should be a single field + ctor + static field.
Owen1212055
left a comment
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.
merger should cleanup style
Add the ability to load plugins for directories other than the configured main plugin directory. Useful in container like contexts with features like Image Volumes
Plugins are still created with the main plugin directory as the data directory so this should be basically transparent.