Skip to content
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

Native quarkus-amazon-lambda-http -- runtime provided is no longer supported #39161

Closed
xstefank opened this issue Mar 4, 2024 · 1 comment · Fixed by #39163
Closed

Native quarkus-amazon-lambda-http -- runtime provided is no longer supported #39161

xstefank opened this issue Mar 4, 2024 · 1 comment · Fixed by #39163

Comments

@xstefank
Copy link
Member

xstefank commented Mar 4, 2024

Describe the bug

When trying native deployment with quarkus-amazon-lambda-http (sam.native.yaml) it fails currently with AWS lambda:

REATE_FAILED AWS::Lambda::Function QuarkusRestServicesNative Resource handler returned message: "The runtime parameter of provided is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (provided.al2023) while creating or updating functions. (Service: Lambda, Status Code: 400, lambda

Expected behavior

Lambda deploys as expected.

Actual behavior

Lambda doesn't deploy to AWS.

How to Reproduce?

Native deploys to AWS.

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

Fix is rather easy (also currently workaround). In target/sam.native.yaml change:

- Runtime: provided
+ Runtime: provided.al2023
@xstefank xstefank added the kind/bug Something isn't working label Mar 4, 2024
Copy link

quarkus-bot bot commented Mar 4, 2024

/cc @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda), @zakkak (native-image)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant