You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea here that we can extend the existing 'asyncapi generate' command to generate platform commands to create/configure the topics.
How will this change help?
This enables the user to leverage the asyncapi file as a form of infrastructure as code.
Screenshots
No response
How could it be implemented/designed?
On the assumption that kafka is the most popular event broker this enhancement would take the list of topic names from the ayncapi yml file, and output a set of 'kafka' style command to config the needed topics.
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Why do we need this improvement?
The idea here that we can extend the existing 'asyncapi generate' command to generate platform commands to create/configure the topics.
How will this change help?
This enables the user to leverage the asyncapi file as a form of infrastructure as code.
Screenshots
No response
How could it be implemented/designed?
On the assumption that kafka is the most popular event broker this enhancement would take the list of topic names from the ayncapi yml file, and output a set of 'kafka' style command to config the needed topics.
The existing cli supports these two options currently
and i'd foresee a 3rd flavour called 'platform'
which based on the broker type in yml file we'd call the relevant platform-template module.
🚧 Breaking changes
No
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: