We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The current plugin architecture is complex in how it pulls in lab-defined code, and it doesn't allow plugins to bring their own dependencies.
We should allow plugins to be specified by extending Sparrow's core docker image.
Instead of using a directory for plugin discovery, we can use package metadata.
Combined with being more flexible about client-side plugins, we will be able to have a bit of a progressive onramp to plugin development.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The current plugin architecture is complex in how it pulls in lab-defined code, and it doesn't allow plugins to bring their own dependencies.
We should allow plugins to be specified by extending Sparrow's core docker image.
Instead of using a directory for plugin discovery, we can use package metadata.
Combined with being more flexible about client-side plugins, we will be able to have a bit of a progressive onramp to plugin development.
The text was updated successfully, but these errors were encountered: