I would like to be able to assign dead letter queue handler in lift

[Setitch]

Start from the Use-case

For now we can assign the handler for the queue, but when they fails messages goes to the dead letter queue - would be really nice if we could assign handler for that queue too

Example Config

No response

Implementation Idea

deadHandler: . ?

[mnapoli]

Could you detail what you would achieve with this setup?

[Setitch]

Sorry for long delay.

I mean i would like to parse them by common lambda that would be handling dead deadletters

[Setitch]

More details: i have a workflow, that moves the ,,ticket'' from one queue to another (they must be executed in order). But when the ticket goes into deadletter queue, i want to grab it by lambda, try to reexecute it, and if its failing - remove from the deadletters but do some things - close the workflow for the ticket and so on. Without providing the lambda on lift config for dead letter lambda-handler, its quite a task.

[kamalnathlp]

@Setitch did you find any solution? @mnapoli any updates on the issue?

[Setitch]

@kamalnathlp sadly not yet, which is real shame

[fredericbarthelet]

DLQ url and arn are now exposed via variables. You can use those to attach a specific lambda handler.