diff --git a/codegen/sdk-codegen/aws-models/sqs.json b/codegen/sdk-codegen/aws-models/sqs.json index 364285b06e3..233b0853b67 100644 --- a/codegen/sdk-codegen/aws-models/sqs.json +++ b/codegen/sdk-codegen/aws-models/sqs.json @@ -1344,7 +1344,7 @@ } ], "traits": { - "smithy.api#documentation": "
Cancels a specified message movement task.
\nA message movement can only be cancelled when the current status is\n RUNNING.
\nCancelling a message movement task does not revert the messages that have\n already been moved. It can only stop the messages that have not been moved\n yet.
\nCancels a specified message movement task. A message movement can only be cancelled\n when the current status is RUNNING. Cancelling a message movement task does not revert\n the messages that have already been moved. It can only stop the messages that have not\n been moved yet.
\nThis action is currently limited to supporting message redrive from dead-letter queues (DLQs) only. In this context, the source\n queue is the dead-letter queue (DLQ), while the destination queue can be the\n original source queue (from which the messages were driven to the\n dead-letter-queue), or a custom destination queue.
\nCurrently, only standard queues are supported.
\nOnly one active message movement task is supported per queue at any given\n time.
\nGets the most recent message movement tasks (up to 10) under a specific source\n queue.
" + "smithy.api#documentation": "Gets the most recent message movement tasks (up to 10) under a specific source\n queue.
\nThis action is currently limited to supporting message redrive from dead-letter queues (DLQs) only. In this context, the source\n queue is the dead-letter queue (DLQ), while the destination queue can be the\n original source queue (from which the messages were driven to the\n dead-letter-queue), or a custom destination queue.
\nCurrently, only standard queues are supported.
\nOnly one active message movement task is supported per queue at any given\n time.
\nA list of queue URLs, up to 1,000 entries, or the value of MaxResults
that you sent in\n the request.
A list of queue URLs, up to 1,000 entries, or the value of MaxResults
\n that you sent in the request.
Deletes the messages in a queue specified by the QueueURL
\n parameter.
When you use the PurgeQueue
action, you can't retrieve any messages\n deleted from a queue.
The message deletion process takes up to 60 seconds. We recommend waiting for 60\n seconds regardless of your queue's size.
\nMessages sent to the queue before you call\n PurgeQueue
might be received but are deleted within the next\n minute.
Messages sent to the queue after you call PurgeQueue
\n might be deleted while the queue is being purged.
Deletes available messages in a queue (including in-flight messages) specified by the\n QueueURL
parameter.
When you use the PurgeQueue
action, you can't retrieve any messages\n deleted from a queue.
The message deletion process takes up to 60 seconds. We recommend waiting for 60\n seconds regardless of your queue's size.
\nMessages sent to the queue before you call\n PurgeQueue
might be received but are deleted within the next\n minute.
Messages sent to the queue after you call PurgeQueue
\n might be deleted while the queue is being purged.
Starts an asynchronous task to move messages from a specified source queue to a\n specified destination queue.
\nThis action is currently limited to supporting message redrive from\n dead-letter queues (DLQs) only. In this context, the source queue is the\n dead-letter queue (DLQ), while the destination queue can be the original\n source queue (from which the messages were driven to the dead-letter-queue),\n or a custom destination queue.
\nCurrently, only standard queues are supported.
\nOnly one active message movement task is supported per queue at any given\n time.
\nStarts an asynchronous task to move messages from a specified source queue to a\n specified destination queue.
\nThis action is currently limited to supporting message redrive from queues\n that are configured as dead-letter queues (DLQs) of other Amazon SQS queues only. Non-SQS\n queue sources of dead-letter queues, such as Lambda or Amazon SNS topics, are\n currently not supported.
\nIn dead-letter queues redrive context, the\n StartMessageMoveTask
the source queue is the DLQ, while the\n destination queue can be the original source queue (from which the messages\n were driven to the dead-letter-queue), or a custom destination queue.
Currently, only standard queues support redrive. FIFO queues don't support\n redrive.
\nOnly one active message movement task is supported per queue at any given\n time.
\nThe ARN of the queue that contains the messages to be moved to another queue.\n Currently, only dead-letter queue (DLQ) ARNs are accepted.
", + "smithy.api#documentation": "The ARN of the queue that contains the messages to be moved to another queue.\n Currently, only ARNs of dead-letter queues (DLQs) whose sources are other Amazon SQS queues\n are accepted. DLQs whose sources are non-SQS queues, such as Lambda or Amazon SNS topics, are\n not currently supported.
", "smithy.api#required": {} } },