Open tinyg210 opened 10 months ago
I guess there is a misunderstanding on who's who.
io.quarkiverse.amazonservices:quarkus-amazon-lambda
is the quarkus wrapper around the lambda client from the aws sdk to manage lambda while io.quarkus:quarkus-amazon-lambda
is the extension to build applications to be run in lambda. The documentation of the latter is https://quarkus.io/guides/aws-lambda.
Regarding the quarkiverse extension (sdk client), we do not currently provide a thoroughfull quickstart but you can look into our integration tests. You should pay attention to the test case and how we create a test lambda application in DevServices for AWS.
Those two extensions should work together so that you may be able to start/stop/create/delete a lambda application from a lambda application.
Hi, I'm trying to follow the docs for the Dev Services for Amazon Services, particularly the one for Lambda that uses LocalStack. I run into a few issues and I'm not sure if the docs are correct since there's no linked sample to this particular scenario.
My setup: Apache Maven 3.9.4 Java version: 17.0.3, vendor: Oracle Corporation Default locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
amazon-lambda
:results into:
I then choose
io.quarkus:quarkus-amazon-lambda
and the project is created, with a Person entity and a Lambda function. I add the necessary dependency as instructed.Running
mvn clean package
fails with the following stack trace:There is no LocalStack container starting while running the test, but the docs say that
Quarkus Amazon Services automatically starts a LocalStack container in dev mode and when running tests.
I added how the project looks at the point of failure: https://github.com/tinyg210/sample-quarkus-lambda-from-docs
There is a lot of abstraction and "magic" behind the Dev Services and I can't tell what is missing and if in fact something is missing. Btw, Lambda functions in LocalStack spin up in a separate container, but if the Dev Services are using Testcontainers in the background, that should not be an issue.
Can someone please explain how this works behind the scenes and what's missing from this setup?