Fix the API documention routing issue when serving the API trough AWS API Gateway #24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fenkiou
force-pushed
the
fix-api-doc-routing
branch
from
728dc73 to
1cabc1d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As zappa is using AWS API Gateway and we didn't configure a dedicated domain name, the stage is appended to the URL that serves the API.
For example for staging:
https://pdkwql16gl.execute-api.eu-west-3.amazonaws.com/staging/openapiSo those changes read the
STAGEenv variable and create the dedicatedServerto fix the routing issue we have in swagger/redoc/rapidoc.Without
STAGE:With
STAGE=staging:Actual value in staging:
