So we cannot just run a docker image for a gateway, we will also need an entire CI process to use this paradigm? Generally, when we use the term "plugin" in industry, this means we do not have to run a compiler.

Crates are still an avenue for supply chain compromise, they come from random developers. We've seen it before and I expect we will see in more frequently for a while, until out industry gets really serious about all the things around this.

▲

Andydy25 4 hours ago | parent | next [-]

We had a Docker image, but pulled it before launch because some APIs might still change. You have to build the Docker images, but we have GitHub releases for binaries.

We have configurable template plugins for common things like adding vendors and formats. No rebuild needed for config changes, but if you want custom logic beyond those templates, you need to compile it in.

And yes, crates still have supply-chain risks. I just meant you can review the source you’re adding, unlike a binary you don’t know.

	▲	verdverm 4 hours ago \| parent [-]
		No one at our org knows rust, so "reading the source" is not possible, and we know people don't actually do this anyway. I would recommend a batteries included approach. You can see a similar difference between adoption of OpenCode and Pi in the harness space. And get the image published, a changing API is no reason not to have one. Every project evolves their API and users know how to handle this situation.

▲

Andydy25 3 hours ago | parent | prev [-]

Yeah, ours are more like GStreamer’s statically compiled plugins. We might consider WebAssembly in the future if there’s a need for it.