Lovro Mažgon

I moved this issue to the main Conduit repo, as the WASI Preview 2 support needs to be added on the host (i.e. Conduit).

A lot, if not all of the code, needed for auto-generating Avro schemas can be found [here](https://github.com/ConduitIO/conduit/blob/main/pkg/plugin/processor/builtin/impl/avro/schemaregistry/avro/extractor.go). The utilities mentioned in both SDKs can be placed in conduit-commons, so we...

Shipped in https://github.com/ConduitIO/conduit/releases/tag/v0.11.0

Thanks for reporting this @nickchomey! Even though it's clearly a bug, I see it as pretty low-priority, as the workaround is straightforward - split the pipelines into separate configuration files....

This could also include https://github.com/ConduitIO/conduit/issues/2268

I don't think we will switch just now, mainly for 3 reasons - I think it's too early to tell that the fork will be better maintained than the original...

If I'm not mistaken, it only happens if you first have `status: running` and then change it to `status: stopped`.

I'll add some more info for when we decide to tackle this. Currently the fields in our proto API definition are not marked with the `optional` keyword, meaning that field...

Hmm, where did you get that example? It's not what I'm seeing in Swagger:  We made a decision soon at the start of the project to let Conduit handle...

This feature would be great to have, but we currently have higher priority items on our roadmap. Although, if you wanted to add this feature we are happy to assist...