-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add support using sandbox functionality in official releases #3677
Comments
@nknize What do you think about this proposal? Since a user has to explicitly install a plugin, and the fact they are located in a "sandbox" directory, this seems like a reasonable process akin to enabling a feature flag and would greatly reduce the friction for users experimenting with a sandbox plugin.
@mattweber The "option" here is just to install the plugin since sandbox features are inherently plugins. Does that make sense to you or were you thinking about something else? /cc @reta |
+1 to @andrross suggestion, alrenatively we could publish sandbox plugin ZIPs into well known repository so people could use it (and make |
+1 |
We could definitely publish the zips just like native plugins today which should help install these plugins. |
@saratvemulapalli Should we just remove it? The concept of the sandbox seems inherently optional to me. I could imagine a feature being promoted from |
Could we combine it with a feature flag? The |
Without a way for people to try out the sandboxed modules, there is less chance that we can learn from the experimental usage. |
Is your feature request related to a problem? Please describe.
Not being able to use sandbox features unless using a snapshot. Snapshots are not published for all release formats, ie. docker images so it is not easy to experiment/test/play with sandbox features.
Describe the solution you'd like
I would like sandbox features built and shipped with official releases and then have some sort of startup option to enable their use. Enabling a sandbox feature would imply the user opting into experimental features and understands it is unsupported.
Describe alternatives you've considered
Building from source.
Additional context
I am excited to try concurrent search plugin
The text was updated successfully, but these errors were encountered: