Skip to content

SQS: start_message_move_task(), list_message_move_tasks(), cancel_message_move_task() - #10558

Open
dhiraj9087 wants to merge 1 commit into
getmoto:masterfrom
dhiraj9087:sqs-message-move-tasks
Open

dhiraj9087 wants to merge 1 commit into
getmoto:masterfrom
dhiraj9087:sqs-message-move-tasks

Conversation

@dhiraj9087

Copy link
Copy Markdown

Implements the SQS message move task operations (DLQ redrive). Closes #10557.

  • start_message_move_task moves the messages from a dead-letter queue to DestinationArn, or, without it, back to the queue each message was moved from. When the redrive policy moves a message to the DLQ, the source queue ARN is now recorded on the message for this. A message sent directly to the DLQ goes to the source queue if the DLQ has exactly one, and stays in the DLQ otherwise.
  • Moved messages get a fresh receive state, so they are not moved straight back to the DLQ on their next receive.
  • Messages are moved immediately, so tasks are COMPLETED as soon as they are created: list_message_move_tasks doesn't return a TaskHandle (AWS only returns it for RUNNING tasks), and cancel_message_move_task raises UnsupportedOperation for existing tasks. Both are documented in the docstrings.
  • Errors: ResourceNotFoundException for unknown source, destination or task handle, UnsupportedOperation when the source is not a DLQ, InvalidParameterValue for MaxNumberOfMessagesPerSecond outside 1-500 and MaxResults outside 1-10.
  • Updated docs/docs/services/sqs.rst and IMPLEMENTATION_COVERAGE.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Title: SQS: implement start_message_move_task, list_message_move_tasks and cancel_message_move_task

1 participant