-
Notifications
You must be signed in to change notification settings - Fork 81
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
API Gateway Proxy Integration payload format 2.0 incompatible #1317
Comments
While working on this, you might want to consider if you want to add support for Application Load Balancers. The request / response format is very similar. |
This is also a blocker for using lambda function URLs, which only support Payload format version 2.0. |
Guys, any plans to support ALB payload on this issue? If not lets open a new one to separated conrtibuition. |
@sdelamo @alvarosanchez @msailes , any ETA on this one? |
Currently, if you select HttpLambdaIntegration integration = HttpLambdaIntegration.Builder.create("HttpLambdaIntegration", function)
.payloadFormatVersion(VERSION_1_0)
.build();
HttpApi api = HttpApi.Builder.create(this, "micronaut-function-api")
.defaultIntegration(integration)
.build(); |
@sdelamo , we require ALB Lambda Integration. Do you have any guidance on how to implement this? I would like to give it a shot. |
Micronaut Framework 4.0 supports v1, v2 and ALB events. |
Expected Behavior
API Gateway HTTP API using proxy integration with a Lambda running Micronaut should work by default
Actual Behaviour
Micronaut silently fails to parse parameters from the default Proxy Integration payload format (2.0) and so every request is read as a
GET /
(and it is very, very difficult to troubleshoot)Steps To Reproduce
Micronaut Application
from Micronaut Launch using all defaults, with the 'aws-lambda' featureio.micronaut.function.aws.proxy.MicronautLambdaHandler
ANY /{proxy+}
route to the Micronaut lambdaBookController.save
Environment Information
micronaut-cli.yml
Example Application
No response
Version
3.4.0
The text was updated successfully, but these errors were encountered: