Comment by rileycalhoun022
11 hours ago
The compile-time choice makes sense for a gateway: plugins sit in the hot path and often need database or queue access, which is awkward to expose through a WASM sandbox. The cost is the workflow verdverm points out: there is no prebuilt image to just pull and run. Do you plan to publish an official build with the default plugin set, for people who don't need custom plugins?
We do have an official build on GitHub Releases with first-party plugins built in.
Honestly one of the coolest things you can do for this sort of problem offer a version of the Talos Image Factory, where people can select the combination of plugins and the architecture and get a build.
There can be a lot of permutations to create of course but each one only needs to be built once per version you release.
To limit permutations you can always create pre-selected bundles of related plugins (like package groups on Linux distros) and let people select those bundles. They can always fall back to building it themselves if they really need to be picky about the plugin selection.