-
Notifications
You must be signed in to change notification settings - Fork 16
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
Configuration error at 'functions[function-name]' unrecognized property 'deadLetter' #46
Comments
Same issue here Your Environment Information --------------------------- |
Same issue here too
|
@jordanmaxfightcamp @johannesdr-tb @carlosroberto555 Looks like Serverless now has a native way to handle dead letter queues which should remove the need for this plugin. (The plugin readme mentions "At the time this plugin was developed AWS Cloudformation (and serverless) did not support the DeadLetterConfig property of the Lambda", which seems to imply they now do support that property.) |
@herstand thanks for your comment.
But the following configuration only works with SNS, when using SQS it is still necessary to use this plugin |
Was anyone able to get this to work? |
Any updates on this issue? |
Still have this issue. :( |
Please,merge the fixing PR. |
Any chance of merging this one? |
hope this PR is merged soon! |
I wasn't really familiar with Lambda DLQs when I hit this issue, so this is what I learned in case it helps anyone. Lambda Dead Letter queues are not still supported by Serverless natively even in v3 (as opposed to SQS DLQs, which I think are supported). In 2019, AWS launched Lambda "destinations" which has the same functionality (and more) and is also "preferred". From the launch blog...
Destinations are supported by Serverless natively so there's a possibility to switch to "Destinations" and you don't need this plugin anyone. The payload format that is received by the DLQ when using Destinations is slightly different so you might need minor code changes if you have code that reads from the DLQ. |
Receiving this error after trying to use this plugin:
here is my code:
Any suggestions? not sure what im doing wrong.
The text was updated successfully, but these errors were encountered: