-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
feat: serve swagger UI in LocalStack #11509
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
Conversation
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 3m 28s ⏱️ Results for commit 0b93328. ♻️ This comment has been updated with latest results. |
7a98747
to
ee1daaf
Compare
e3c0ed7
to
25c6c9b
Compare
f35487b
to
0f44ccc
Compare
added localstack.http.resources.swagger all the swagger stuff in there
Thanks Viren for the suggestion
@thrau I opted to create a |
i think this is good for now! that said, the http package was originally really meant as the package for our http framework library. anything concrete such as internal endpoints, should actually be part of some services/application package, which is currently only |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! looking forward to seeing this in action :-)
Motivation
We recently introduced OpenAPI specs for different LocalStack packages (
localstack
andlocalstack.pro.core
at the moment).These specs document all the internal developer endpoints we serve in LocalStack.
To allow users to navigate those specs, we want to serve the SwaggerUI directly within LocalStack.
Changes
http://localhost.localstack.cloud:4566/_localstack/swagger
) that serves built OAS spec with a SwaggerUI. The UI is rendered withjinja2
and lives in thelocalstack.static
package.