Attached nested inline syntax for ksml-runner.yaml works in docker compose, messages get produced and processed correctly as verified in Kowl UI.
Do we want to support this syntax? It’s a pretty nice way to have just 1 file for very small definitions:
-
KSML configuration
-
processor definition
-
producer definition
-
If we do support the syntax, then we need to ensure that the KSML definition itself is also supported in the KSML runner config. That would require us to align both Implementations, would it not? Needs some research.
Validating this ksml-runner.yaml with a schema will be tricky of course, currently it fails(screenshot). But should be possible.
ksml-runner.yaml
producer.yaml
docker-compose.yml
kowl-ui-config.yaml
Attached nested inline syntax for
ksml-runner.yamlworks in docker compose, messages get produced and processed correctly as verified in Kowl UI.Do we want to support this syntax? It’s a pretty nice way to have just 1 file for very small definitions:
KSML configuration
processor definition
producer definition
If we do support the syntax, then we need to ensure that the KSML definition itself is also supported in the KSML runner config. That would require us to align both Implementations, would it not? Needs some research.
Validating this
ksml-runner.yamlwith a schema will be tricky of course, currently it fails(screenshot). But should be possible.ksml-runner.yaml
producer.yaml
docker-compose.yml
kowl-ui-config.yaml