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
I'll start off by saying that the dataplaneapi is an amazing alternative to the old way of controlling the runtime config!
I would love though, if I could use swagger-ui to build on top of dataplane api so, it would be great if you could either include swagger-ui in the dataplaneapi, so we could run calls directly from it or, if you could at least expose the specifications endpoints (/v2/specification and /v2/specification_openapiv3) without authentication, so we can start our own stagger-ui and point it to use those specs.
Thank you!
The text was updated successfully, but these errors were encountered:
Edit #1: I just saw that with OAS3, one can specify the servers in the specifications file. It sort of solves the issue, it's just not as easy as being able to specify an endpoint pointing to the OAS3 spec output. (/v2/specification_openapiv3)
Hello,
I'll start off by saying that the dataplaneapi is an amazing alternative to the old way of controlling the runtime config!
I would love though, if I could use swagger-ui to build on top of dataplane api so, it would be great if you could either include swagger-ui in the dataplaneapi, so we could run calls directly from it or, if you could at least expose the specifications endpoints (/v2/specification and /v2/specification_openapiv3) without authentication, so we can start our own stagger-ui and point it to use those specs.
Thank you!
The text was updated successfully, but these errors were encountered: