-
Notifications
You must be signed in to change notification settings - Fork 603
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
S3EventNotification can't be deserialized #1116
Comments
First we have a test for S3 event and it seems to be working fine.
Can you please look at it and see what's going on? |
@olegz is there any plan on releasing 4.1.2 and may be move this issue to next release. Thank you |
I am not following your last comment. Yes we will be releasing 4.1.2 at some point, but are you saying that your issue is resolved with 4.1.2-SNAPSHOT? |
I trying to say that I am waiting 4.1.2 to be released and found this |
Ok, the 4.1.2 is available, so I am closing this |
Describe the bug
I'm really facing up with S3 event lambda function deserialization.
I'm getting:
Detailed trace:
Sample
Here you can find code repo.
I'm able to reach my function since I've added
spring-cloud-starter-function-web
dependency.Then, here my test s3 notification:
In order to reach my function via http I'm using:
My Consumer is:
My pom.xml is:
The text was updated successfully, but these errors were encountered: