Pluggability
Summary
Issues:
- [ ] #4355
- [x] #5201
- [x] #7154
- [ ] #7177
- [ ] #7710
- [ ] #6945
- [ ] #5862
- [ ] #6867
- [x] #7073
- [x] #6313
- [ ] #4162
- [ ] #4163
- [ ] #7743
Related:
- [ ] #6615
- [ ] #4158
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
WASM / WASI could be a huge boon for plugins as it allows for code from almost any language to be executed in a secure, sandboxed way.
There is already the WASM Executor plugin, but we could potentially have built-in support for it and utilize WASM in several different places, including in the Controller and Server themselves, not just in ephemeral executors.
We could detect a WASM binaries on the filesystem and load them for different plugins, so a user could then have a custom image or volume mount with their binaries.
Implementation-wise, there do exist some great tools for this already, Exitsm in particular is an SDK for WASM-powered plugin systems and has an existing Go SDK.