You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
Fix is rather easy (also currently workaround). In target/sam.native.yaml change:
The text was updated successfully, but these errors were encountered: