Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support asyncapi mqtt streetlights mapping to kafka streetlights #947

Closed
jfallows opened this issue Apr 17, 2024 · 0 comments · Fixed by #997
Closed

Support asyncapi mqtt streetlights mapping to kafka streetlights #947

jfallows opened this issue Apr 17, 2024 · 0 comments · Fixed by #997
Assignees
@bmaidics
Labels
story Feature description from user's perspective

Comments

@jfallows
Copy link
Contributor

Describe the desired outcome from the user's perspective
As devops, I want to map AsyncAPI mqtt streetlights example to AsyncAPI kafka streetlights example.

Acceptance criteria

  • Publishing to various topics in mqtt results in the same named topics being used in kafka

Additional context
mqtt-kafka requires with topic: …/${params.streetlightId}/… to propagate dynamic topic name to kafka during mapping
asyncapi proxy needs to generate with: ... ${params.streetlightId} internally
@jfallows jfallows added the story Feature description from user's perspective label Apr 17, 2024
@bmaidics bmaidics linked a pull request May 8, 2024 that will close this issue
Support asyncapi mqtt streetlights mapping to kafka streetlights #997
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bmaidics bmaidics

Labels
story Feature description from user's perspective
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support asyncapi mqtt streetlights mapping to kafka streetlights bmaidics/zilla
2 participants
@jfallows @bmaidics