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
Is your feature request related to a problem? Please describe.
I want to make use of AWS Lambdas DeadLetterQueue feature for errors while processing async Lambda invocations. But right now it's not possible to do a async invocation while it could be.
Describe the solution you'd like
I'd like to have a InvocationType parameter in the Lambda trigger.
Describe alternatives you've considered
For this case it's all about error handling. When I execute a Lambda function and it fails I want to be able to act on it. It would be awesome if argo-events itself has this feature, but for now I don't see a way to handle failed triggers within argo-events.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
@VaibhavPage, sure. When you configure a DeadLetterQueue (DLQ) in a Lambda function, failed invocations go straight to this queue from where another process could pick them up and report them or try the same event again but maybe with a more resilient and failure tolerant second function. Unfortunately DLQs are only considered when you do an asynchronous invocation of a Lambda function. So the Lambda trigger has to be extended to support the additional parameter.
whynowy
added a commit
to whynowy/argo-events
that referenced
this issue
Apr 22, 2021
Is your feature request related to a problem? Please describe.
I want to make use of AWS Lambdas DeadLetterQueue feature for errors while processing async Lambda invocations. But right now it's not possible to do a async invocation while it could be.
Describe the solution you'd like
I'd like to have a InvocationType parameter in the Lambda trigger.
Describe alternatives you've considered
For this case it's all about error handling. When I execute a Lambda function and it fails I want to be able to act on it. It would be awesome if argo-events itself has this feature, but for now I don't see a way to handle failed triggers within argo-events.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: