We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There remain a problem with the links in openapi doc that do not include the default stage prefix used when deploying with the serverless framework.
The OpenAPI doc is well served and displayed but the links used to test the API do not work.
Note: this issue would disappear if using a custom domain (like dev.boa.my-domain.com and prod/boa.my-domain.com).
For example: OpenAPI is pointing to this URL (without the dev prefix):
https://1rq5nf92sb.execute-api.eu-west-1.amazonaws.com/v1/server/all_default_models
while content is served from the same URL (but with the dev prefix):
https://1rq5nf92sb.execute-api.eu-west-1.amazonaws.com/**dev**/v1/server/all_default_models
Open API spec links should work in sls deployment
Related issues that may be helpfull
The text was updated successfully, but these errors were encountered:
https://fastapi.tiangolo.com/advanced/behind-a-proxy/
Sorry, something went wrong.
The trik seems to use root_path instead of openapi_prefix see
root_path
openapi_prefix
Commit 6fe3498 should fix it.
Can I close this issue since 6fe3498 has been merged?
Yes, thanks, I close it now.
demeringo
No branches or pull requests
Bug description
There remain a problem with the links in openapi doc that do not include the default stage prefix used when deploying with the serverless framework.
The OpenAPI doc is well served and displayed but the links used to test the API do not work.
Note: this issue would disappear if using a custom domain (like dev.boa.my-domain.com and prod/boa.my-domain.com).
For example:
OpenAPI is pointing to this URL (without the dev prefix):
https://1rq5nf92sb.execute-api.eu-west-1.amazonaws.com/v1/server/all_default_models
while content is served from the same URL (but with the dev prefix):
https://1rq5nf92sb.execute-api.eu-west-1.amazonaws.com/**dev**/v1/server/all_default_models
Expected behavior
Open API spec links should work in sls deployment
JSON OUTPUT
Additional context
Related issues that may be helpfull
The text was updated successfully, but these errors were encountered: