-
-
Notifications
You must be signed in to change notification settings - Fork 696
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.
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
[3.0.0] Serve bindings JSON Schema files via https://asyncapi.com/bindings #870
Comments
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 ❤️ |
still relevant |
Weep! this should be reopened! |
@smoya next time do not wait for us to reopen but go ahead and open new issue 👍🏼 |
I tested now and It worked. But for some reason, I couldn't reopen it and I assumed it was because issues closed by bot couldn't be reopened. |
wait, so is it suppose to be open or close 😃 |
Opened, as now. |
We need to either create a new or modify the following Netlify edge-function https://github.com/asyncapi/website/blob/master/netlify/edge-functions/serve-definitions.ts and add a new redirection rule into https://github.com/asyncapi/website/blob/master/netlify.toml |
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 ❤️ |
Still valid |
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 ❤️ |
This is still needed, for bindings and extensions |
Originally posted by @smoya in asyncapi/spec-json-schemas#225 (comment)
Serve schemas for bindings via https://asyncapi.com/bindings .
Those will be located in https://github.com/asyncapi/spec-json-schemas/tree/next-major-spec/bindings
Serving JSON Schema files through asyncapi.com is done thanks to the following Netlify Edge Function: https://github.com/asyncapi/website/blob/master/netlify/edge-functions/serve-definitions.ts
Ids like http://asyncapi.com/bindings/kafka/0.4.0/message.json should be reachable as well by HTTP in the same address as the id name.
Fixes asyncapi/spec-json-schemas#493
The text was updated successfully, but these errors were encountered: