-
Notifications
You must be signed in to change notification settings - Fork 420
SnsSqsEnvelope/SnsNotificationModel - Missing fields for FIFO SNS -> FIFO SQS -> Lambda #1590
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
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
thanks for raising that to us @plondino! That's because SNS FIFO changed their contract from non-FIFO thus the breakage. I'll create a PR marking these fields as cc @ran-isenberg for FYI |
Until this is released, you can also optionally set |
@plondino we're making a release now (v1.31.1) to include this fix. We've also recreated SNS FIFO + SQS FIFO + Lambda to ensure there wasn't anything else missing for the validation. Lambda Layer v39 should be available in all regions in approximately 15m |
This is now released under 1.31.1 version! |
Expected Behaviour
I have a lambda triggered by a FIFO SQS which is subscribed to a FIFO SNS (see https://docs.aws.amazon.com/sns/latest/dg/fifo-message-delivery.html for this format).
The payload I receive is:
When I unwrap the SNS message I get:
I would expect the parser.envelopes.SnsSqsEnvelope or the SnsNotificationModel to be able to validate and unwrap this.
Current Behaviour
I get an error:
I found #265 which seemed similar but in this case the fields are actually missing in the SNS I receive in AWS, not just renamed.
Code snippet
Possible Solution
No response
Steps to Reproduce
See above
AWS Lambda Powertools for Python version
latest
AWS Lambda function runtime
3.9
Packaging format used
PyPi
Debugging logs
No response
The text was updated successfully, but these errors were encountered: