Consider supporting multiple AsyncAPI Docs as config source.
Opened this issue · 3 comments
Just to add some context, the app configures the Kafka proxy based on the servers section and some properties (actually extensions) you must configure on the server(s).
Just to simplify, It basically configures a local port to map to a remote Kafka broker.
The question is: What are the usecase for supporting multiple AsyncAPI files?
As example, I could think there might be use cases where users might want to configure the app to act as Kafka proxy for several Kafka clusters. Clusters that could be found in different asyncapi.yaml files.
However, I see some technical complexity in here, since same servers could be declared in several files but with different names, same for channels related to those servers.
Is there a concise reason we might want to support configuring the event-gateway from several files instead of just using one?
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Thank you for your patience ❤️
I think that it's still relevant :)
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Thank you for your patience ❤️