-
Notifications
You must be signed in to change notification settings - Fork 71
Closed
Labels
storyFeature description from user's perspectiveFeature description from user's perspective
Description
Describe the desired outcome from the user's perspective
As an AsyncAPI consumer, I want to configure zilla as mqtt proxy to kafka using asyncapi.yaml more directly in zilla.yaml.
Acceptance criteria
asyncapiserverbinding configured viamqttasyncapi.yamlasyncapiclientbinding configured viakafkaasyncapi.yamlasyncapiproxybinding configured viamqttandkafkaasyncapi.yaml- only
asyncapiserver,proxyandclientbindings needed to configuremqtttokafkaproxy
Additional context
Syntax similar to the following in zilla.yaml using composite bindings.
bindings:
asyncapi_server:
type: asyncapi
kind: server
options:
specs:
- mqtt/asyncapi.yaml
exit: asyncapi_proxy
asyncapi_proxy:
type: asyncapi
kind: proxy
options:
specs:
- mqtt/asyncapi.yaml
- kafka/asyncapi.yaml
routes:
- when:
- operation: ... # mqtt asyncapi operation id
exit: asyncapi_client
with:
operation: ... # kafka asyncapi operation id
asyncapi_client:
type: asyncapi
kind: client
options:
specs:
- kafka/asyncapi.yamlReactions are currently unavailable
Metadata
Metadata
Assignees
Labels
storyFeature description from user's perspectiveFeature description from user's perspective