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'm deploying an API written in Swagger (OAS3) behind AWS API Gateway. I can't import it into API Gateway because it seems as if they still only support 2.0.
That's fine. I don't mind that so much, but the problem is it messes with my Swagger UI. API Gateway puts the stage name in the URL but the swagger/connexion app isn't able to "see" this. As a result the Explore bar has the wrong path to the spec file.
It loads up with /swagger_url/openapi.spec but needs to be changed to /aws_stage_name/swagger_url/openapi.spec in order to load properly in the console.
I took a look at the ui stuff myself but am not a front end guy so had absolutely no idea what I was looking at. :)
The text was updated successfully, but these errors were encountered:
I'm deploying an API written in Swagger (OAS3) behind AWS API Gateway. I can't import it into API Gateway because it seems as if they still only support 2.0.
That's fine. I don't mind that so much, but the problem is it messes with my Swagger UI. API Gateway puts the stage name in the URL but the swagger/connexion app isn't able to "see" this. As a result the Explore bar has the wrong path to the spec file.
It loads up with
/swagger_url/openapi.spec
but needs to be changed to/aws_stage_name/swagger_url/openapi.spec
in order to load properly in the console.I took a look at the ui stuff myself but am not a front end guy so had absolutely no idea what I was looking at. :)
The text was updated successfully, but these errors were encountered: