-
Notifications
You must be signed in to change notification settings - Fork 3k
Move aws-lambda to new dev services model, starting services after augmentation #48753
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
Move aws-lambda to new dev services model, starting services after augmentation #48753
Conversation
🎊 PR Preview db3b06b has been successfully built and deployed to https://quarkus-pr-main-48753-preview.surge.sh/version/main/guides/
|
7113ac1
to
671c9a4
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
671c9a4
to
2d851a0
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
2d851a0
to
5f92c20
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
5f92c20
to
a13d780
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
a13d780
to
91ff7be
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
A small question. Otherwise, this is ok for me before #48785
...deployment/src/main/java/io/quarkus/amazon/lambda/deployment/DevServicesLambdaProcessor.java
Outdated
Show resolved
Hide resolved
91ff7be
to
bd7a172
Compare
Status for workflow
|
Status for workflow
|
Resolves #48006
This doesn't fully get the lambda dev service to how it was before the test classloading rewrite, because ephemeral ports still don't work. Fixing that needs some dev service infra changes and some fussing with config priorities, so I've moved it to its own issue: #48784