-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
swagger-ui endpoint not accessible in AWS Lambda #8226
Comments
/cc @patriot1burke |
Hi, does the same happen with a non lambda application? |
Haven't tired deploying to any actual server. But looks like lambda-http extension is somehow blocking /openapi endpoint which is being called in SwaggerBundleUI in index.html. If quarkus generates the openapi.json file in root folder during the build phase, can it just use specs instead of url ? |
I think this is a matter that the root path is /api. Is there a way to change swagger to look at a different root path? I'll have time to look at this next week. |
Hello @patriot1burke , Just checking to see if you got a chance to look into this ? Thank you! |
Describe the bug
Making a http call to /swagger-ui/ , the app fails to serve the swagger-ui files. Local Dev mode works fine.
Expected behavior
Opening /swagger-ui/ should load swagger-ui/index.html page
Actual behavior
ERROR [io.qua.ver.htt.run.QuarkusErrorHandler] (vert.x-eventloop-thread-2) HTTP Request to /swagger-ui/index.html failed, error id: bea62c51-a11f-4cb4-8aba-86217c872b1d-1: io.vertx.core.file.FileSystemException: java.nio.file.NoSuchFileException: META-INF/swagger-ui-files/index.html
at io.vertx.core.file.impl.FileSystemImpl$7.perform(FileSystemImpl.java:625)
at io.vertx.core.file.impl.FileSystemImpl$7.perform(FileSystemImpl.java:613)
at io.vertx.core.file.impl.FileSystemImpl.propsBlocking(FileSystemImpl.java:162)
at io.vertx.ext.web.handler.impl.StaticHandlerImpl.lambda$getFileProps$4(StaticHandlerImpl.java:295)
at io.vertx.ext.web.handler.impl.StaticHandlerImpl.wrapInTCCLSwitch(StaticHandlerImpl.java:266)
at io.vertx.ext.web.handler.impl.StaticHandlerImpl.getFileProps(StaticHandlerImpl.java:295)
at io.vertx.ext.web.handler.impl.StaticHandlerImpl.lambda$sendStatic$1(StaticHandlerImpl.java:208)
at io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:330)
at io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:369)
at io.vertx.core.impl.EventLoopContext.lambda$executeAsync$0(EventLoopContext.java:38)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.file.NoSuchFileException: META-INF/swagger-ui-files/index.html
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55)
at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144)
at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99)
at java.nio.file.Files.readAttributes(Files.java:1737)
at io.vertx.core.file.impl.FileSystemImpl$7.perform(FileSystemImpl.java:619)
To Reproduce
Steps to reproduce the behavior:
6.) Try to accessing /swagger-ui/ endpoint
Configuration
Screenshots
(If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
uname -a
orver
:java -version
: java8mvnw --version
orgradlew --version
): maven 3.6.2+Additional context
(Add any other context about the problem here.)
The text was updated successfully, but these errors were encountered: