From f35756158a0a04293de6187f6f20167689e9197c Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Fri, 10 May 2024 01:17:03 -0400 Subject: [PATCH] fix(deps): update module github.com/aws/aws-sdk-go-v2/service/sqs to v1.32.0 (#109) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: co-go --- go.mod | 2 +- go.sum | 2 + sqs.go | 542 +++++++++++++++++++++++++++++++++++---------------------- 3 files changed, 338 insertions(+), 208 deletions(-) diff --git a/go.mod b/go.mod index 8e0c5ac..b471512 100644 --- a/go.mod +++ b/go.mod @@ -7,7 +7,7 @@ require ( github.com/aws/aws-sdk-go-v2 v1.26.1 github.com/aws/aws-sdk-go-v2/config v1.27.12 github.com/aws/aws-sdk-go-v2/service/s3 v1.53.2 - github.com/aws/aws-sdk-go-v2/service/sqs v1.31.4 + github.com/aws/aws-sdk-go-v2/service/sqs v1.32.0 github.com/google/uuid v1.6.0 github.com/stretchr/testify v1.9.0 golang.org/x/sync v0.7.0 diff --git a/go.sum b/go.sum index 0099d8c..5acc89b 100644 --- a/go.sum +++ b/go.sum @@ -208,6 +208,8 @@ github.com/aws/aws-sdk-go-v2/service/sqs v1.31.3 h1:AOQ5bXiVWqoEAv8Ag7zgJoDVhOz3 github.com/aws/aws-sdk-go-v2/service/sqs v1.31.3/go.mod h1:GCHwwK0RX9JVvLYzDDLHCvkD2lMihdqJSQ2kzkVbyhw= github.com/aws/aws-sdk-go-v2/service/sqs v1.31.4 h1:mE2ysZMEeQ3ulHWs4mmc4fZEhOfeY1o6QXAfDqjbSgw= github.com/aws/aws-sdk-go-v2/service/sqs v1.31.4/go.mod h1:lCN2yKnj+Sp9F6UzpoPPTir+tSaC9Jwf6LcmTqnXFZw= +github.com/aws/aws-sdk-go-v2/service/sqs v1.32.0 h1:6SqfD+Oyi6GuoBeSXl0khuW5MFpPJTYcdGHzi86eWiA= +github.com/aws/aws-sdk-go-v2/service/sqs v1.32.0/go.mod h1:lCN2yKnj+Sp9F6UzpoPPTir+tSaC9Jwf6LcmTqnXFZw= github.com/aws/aws-sdk-go-v2/service/sso v1.18.7 h1:eajuO3nykDPdYicLlP3AGgOyVN3MOlFmZv7WGTuJPow= github.com/aws/aws-sdk-go-v2/service/sso v1.18.7/go.mod h1:+mJNDdF+qiUlNKNC3fxn74WWNN+sOiGOEImje+3ScPM= github.com/aws/aws-sdk-go-v2/service/sso v1.19.2 h1:pnj8llQoBAHD4UmbM8UM5GdfycFJKMhgPSeaOyRaZ34= diff --git a/sqs.go b/sqs.go index 568a954..013eb26 100644 --- a/sqs.go +++ b/sqs.go @@ -1,4 +1,4 @@ -// Generated from service/sqs/v1.31.4 +// Generated from service/sqs/v1.32.0 package sqsextendedclient @@ -18,53 +18,67 @@ type SQSClient interface { // config. Config overrides should instead be made on a per-operation basis through // functional options. Options() sqs.Options - // Adds a permission to a queue for a specific principal (https://docs.aws.amazon.com/general/latest/gr/glos-chap.html#P) - // . This allows sharing access to the queue. When you create a queue, you have - // full control access rights for the queue. Only you, the owner of the queue, can - // grant or deny permissions to the queue. For more information about these - // permissions, see Allow Developers to Write Messages to a Shared Queue (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-writing-an-sqs-policy.html#write-messages-to-shared-queue) - // in the Amazon SQS Developer Guide. - // - AddPermission generates a policy for you. You can use SetQueueAttributes to - // upload your policy. For more information, see Using Custom Policies with the - // Amazon SQS Access Policy Language (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-creating-custom-policies.html) - // in the Amazon SQS Developer Guide. + // Adds a permission to a queue for a specific [principal]. This allows sharing access to the + // queue. + // + // When you create a queue, you have full control access rights for the queue. + // Only you, the owner of the queue, can grant or deny permissions to the queue. + // For more information about these permissions, see [Allow Developers to Write Messages to a Shared Queue]in the Amazon SQS Developer + // Guide. + // + // - AddPermission generates a policy for you. You can use SetQueueAttributesto upload your + // policy. For more information, see [Using Custom Policies with the Amazon SQS Access Policy Language]in the Amazon SQS Developer Guide. + // // - An Amazon SQS policy can have a maximum of seven actions per statement. + // // - To remove the ability to change queue permissions, you must deny permission // to the AddPermission , RemovePermission , and SetQueueAttributes actions in // your IAM policy. + // // - Amazon SQS AddPermission does not support adding a non-account principal. // - // Cross-account permissions don't apply to this action. For more information, see - // Grant cross-account permissions to a role and a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) + // Cross-account permissions don't apply to this action. For more information, see [Grant cross-account permissions to a role and a username] // in the Amazon SQS Developer Guide. + // + // [principal]: https://docs.aws.amazon.com/general/latest/gr/glos-chap.html#P + // [Allow Developers to Write Messages to a Shared Queue]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-writing-an-sqs-policy.html#write-messages-to-shared-queue + // [Using Custom Policies with the Amazon SQS Access Policy Language]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-creating-custom-policies.html + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name AddPermission(ctx context.Context, params *sqs.AddPermissionInput, optFns ...func(*sqs.Options)) (*sqs.AddPermissionOutput, error) // Cancels a specified message movement task. A message movement can only be // cancelled when the current status is RUNNING. Cancelling a message movement task // does not revert the messages that have already been moved. It can only stop the // messages that have not been moved yet. - // - This action is currently limited to supporting message redrive from - // dead-letter queues (DLQs) (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html) - // only. In this context, the source queue is the dead-letter queue (DLQ), while - // the destination queue can be the original source queue (from which the messages - // were driven to the dead-letter-queue), or a custom destination queue. - // - Currently, only standard queues are supported. + // + // - This action is currently limited to supporting message redrive from [dead-letter queues (DLQs)]only. + // In this context, the source queue is the dead-letter queue (DLQ), while the + // destination queue can be the original source queue (from which the messages were + // driven to the dead-letter-queue), or a custom destination queue. + // // - Only one active message movement task is supported per queue at any given // time. + // + // [dead-letter queues (DLQs)]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html CancelMessageMoveTask(ctx context.Context, params *sqs.CancelMessageMoveTaskInput, optFns ...func(*sqs.Options)) (*sqs.CancelMessageMoveTaskOutput, error) // Changes the visibility timeout of a specified message in a queue to a new // value. The default visibility timeout for a message is 30 seconds. The minimum - // is 0 seconds. The maximum is 12 hours. For more information, see Visibility - // Timeout (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html) - // in the Amazon SQS Developer Guide. For example, if the default timeout for a - // queue is 60 seconds, 15 seconds have elapsed since you received the message, and - // you send a ChangeMessageVisibility call with VisibilityTimeout set to 10 - // seconds, the 10 seconds begin to count from the time that you make the - // ChangeMessageVisibility call. Thus, any attempt to change the visibility timeout - // or to delete that message 10 seconds after you initially change the visibility - // timeout (a total of 25 seconds) might result in an error. An Amazon SQS message - // has three basic states: + // is 0 seconds. The maximum is 12 hours. For more information, see [Visibility Timeout]in the Amazon + // SQS Developer Guide. + // + // For example, if the default timeout for a queue is 60 seconds, 15 seconds have + // elapsed since you received the message, and you send a ChangeMessageVisibility + // call with VisibilityTimeout set to 10 seconds, the 10 seconds begin to count + // from the time that you make the ChangeMessageVisibility call. Thus, any attempt + // to change the visibility timeout or to delete that message 10 seconds after you + // initially change the visibility timeout (a total of 25 seconds) might result in + // an error. + // + // An Amazon SQS message has three basic states: + // // - Sent to a queue by a producer. + // // - Received from the queue by a consumer. + // // - Deleted from the queue. // // A message is considered to be stored after it is sent to a queue by a producer, @@ -72,282 +86,396 @@ type SQSClient interface { // 2). There is no limit to the number of stored messages. A message is considered // to be in flight after it is received from a queue by a consumer, but not yet // deleted from the queue (that is, between states 2 and 3). There is a limit to - // the number of in flight messages. Limits that apply to in flight messages are - // unrelated to the unlimited number of stored messages. For most standard queues - // (depending on queue traffic and message backlog), there can be a maximum of - // approximately 120,000 in flight messages (received from a queue by a consumer, - // but not yet deleted from the queue). If you reach this limit, Amazon SQS returns - // the OverLimit error message. To avoid reaching the limit, you should delete - // messages from the queue after they're processed. You can also increase the - // number of queues you use to process your messages. To request a limit increase, - // file a support request (https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-sqs) - // . For FIFO queues, there can be a maximum of 20,000 in flight messages (received + // the number of in flight messages. + // + // Limits that apply to in flight messages are unrelated to the unlimited number + // of stored messages. + // + // For most standard queues (depending on queue traffic and message backlog), + // there can be a maximum of approximately 120,000 in flight messages (received // from a queue by a consumer, but not yet deleted from the queue). If you reach - // this limit, Amazon SQS returns no error messages. If you attempt to set the - // VisibilityTimeout to a value greater than the maximum time left, Amazon SQS - // returns an error. Amazon SQS doesn't automatically recalculate and increase the - // timeout to the maximum remaining time. Unlike with a queue, when you change the - // visibility timeout for a specific message the timeout value is applied - // immediately but isn't saved in memory for that message. If you don't delete a - // message after it is received, the visibility timeout for the message reverts to - // the original timeout value (not to the value you set using the - // ChangeMessageVisibility action) the next time the message is received. + // this limit, Amazon SQS returns the OverLimit error message. To avoid reaching + // the limit, you should delete messages from the queue after they're processed. + // You can also increase the number of queues you use to process your messages. To + // request a limit increase, [file a support request]. + // + // For FIFO queues, there can be a maximum of 20,000 in flight messages (received + // from a queue by a consumer, but not yet deleted from the queue). If you reach + // this limit, Amazon SQS returns no error messages. + // + // If you attempt to set the VisibilityTimeout to a value greater than the maximum + // time left, Amazon SQS returns an error. Amazon SQS doesn't automatically + // recalculate and increase the timeout to the maximum remaining time. + // + // Unlike with a queue, when you change the visibility timeout for a specific + // message the timeout value is applied immediately but isn't saved in memory for + // that message. If you don't delete a message after it is received, the visibility + // timeout for the message reverts to the original timeout value (not to the value + // you set using the ChangeMessageVisibility action) the next time the message is + // received. + // + // [Visibility Timeout]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html + // [file a support request]: https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-sqs ChangeMessageVisibility(ctx context.Context, params *sqs.ChangeMessageVisibilityInput, optFns ...func(*sqs.Options)) (*sqs.ChangeMessageVisibilityOutput, error) - // Changes the visibility timeout of multiple messages. This is a batch version of - // ChangeMessageVisibility . The result of the action on each message is reported - // individually in the response. You can send up to 10 ChangeMessageVisibility - // requests with each ChangeMessageVisibilityBatch action. Because the batch - // request can result in a combination of successful and unsuccessful actions, you - // should check for batch errors even when the call returns an HTTP status code of - // 200 . + // Changes the visibility timeout of multiple messages. This is a batch version of ChangeMessageVisibility + // . The result of the action on each message is reported individually in the + // response. You can send up to 10 ChangeMessageVisibilityrequests with each ChangeMessageVisibilityBatch + // action. + // + // Because the batch request can result in a combination of successful and + // unsuccessful actions, you should check for batch errors even when the call + // returns an HTTP status code of 200 . ChangeMessageVisibilityBatch(ctx context.Context, params *sqs.ChangeMessageVisibilityBatchInput, optFns ...func(*sqs.Options)) (*sqs.ChangeMessageVisibilityBatchOutput, error) // Creates a new standard or FIFO queue. You can pass one or more attributes in // the request. Keep the following in mind: + // // - If you don't specify the FifoQueue attribute, Amazon SQS creates a standard - // queue. You can't change the queue type after you create it and you can't convert - // an existing standard queue into a FIFO queue. You must either create a new FIFO - // queue for your application or delete your existing standard queue and recreate - // it as a FIFO queue. For more information, see Moving From a Standard Queue to - // a FIFO Queue (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html#FIFO-queues-moving) - // in the Amazon SQS Developer Guide. - // - If you don't provide a value for an attribute, the queue is created with - // the default value for the attribute. - // - If you delete a queue, you must wait at least 60 seconds before creating a - // queue with the same name. + // queue. + // + // You can't change the queue type after you create it and you can't convert an + // + // existing standard queue into a FIFO queue. You must either create a new FIFO + // queue for your application or delete your existing standard queue and recreate + // it as a FIFO queue. For more information, see [Moving From a Standard Queue to a FIFO Queue]in the Amazon SQS Developer + // Guide. + // + // - If you don't provide a value for an attribute, the queue is created with + // the default value for the attribute. + // + // - If you delete a queue, you must wait at least 60 seconds before creating a + // queue with the same name. // // To successfully create a new queue, you must provide a queue name that adheres - // to the limits related to queues (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/limits-queues.html) - // and is unique within the scope of your queues. After you create a queue, you - // must wait at least one second after the queue is created to be able to use the - // queue. To get the queue URL, use the GetQueueUrl action. GetQueueUrl requires - // only the QueueName parameter. be aware of existing queue names: + // to the [limits related to queues]and is unique within the scope of your queues. + // + // After you create a queue, you must wait at least one second after the queue is + // created to be able to use the queue. + // + // To get the queue URL, use the GetQueueUrl action. GetQueueUrl requires only the QueueName parameter. + // be aware of existing queue names: + // // - If you provide the name of an existing queue along with the exact names and // values of all the queue's attributes, CreateQueue returns the queue URL for // the existing queue. + // // - If the queue name, attribute names, or attribute values don't match an // existing queue, CreateQueue returns an error. // - // Cross-account permissions don't apply to this action. For more information, see - // Grant cross-account permissions to a role and a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) + // Cross-account permissions don't apply to this action. For more information, see [Grant cross-account permissions to a role and a username] // in the Amazon SQS Developer Guide. + // + // [limits related to queues]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/limits-queues.html + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name + // + // [Moving From a Standard Queue to a FIFO Queue]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html#FIFO-queues-moving CreateQueue(ctx context.Context, params *sqs.CreateQueueInput, optFns ...func(*sqs.Options)) (*sqs.CreateQueueOutput, error) // Deletes the specified message from the specified queue. To select the message // to delete, use the ReceiptHandle of the message (not the MessageId which you // receive when you send the message). Amazon SQS can delete a message from a queue // even if a visibility timeout setting causes the message to be locked by another // consumer. Amazon SQS automatically deletes messages left in a queue longer than - // the retention period configured for the queue. The ReceiptHandle is associated - // with a specific instance of receiving a message. If you receive a message more - // than once, the ReceiptHandle is different each time you receive a message. When - // you use the DeleteMessage action, you must provide the most recently received - // ReceiptHandle for the message (otherwise, the request succeeds, but the message - // will not be deleted). For standard queues, it is possible to receive a message - // even after you delete it. This might happen on rare occasions if one of the - // servers which stores a copy of the message is unavailable when you send the - // request to delete the message. The copy remains on the server and might be - // returned to you during a subsequent receive request. You should ensure that your - // application is idempotent, so that receiving a message more than once does not - // cause issues. + // the retention period configured for the queue. + // + // The ReceiptHandle is associated with a specific instance of receiving a + // message. If you receive a message more than once, the ReceiptHandle is + // different each time you receive a message. When you use the DeleteMessage + // action, you must provide the most recently received ReceiptHandle for the + // message (otherwise, the request succeeds, but the message will not be deleted). + // + // For standard queues, it is possible to receive a message even after you delete + // it. This might happen on rare occasions if one of the servers which stores a + // copy of the message is unavailable when you send the request to delete the + // message. The copy remains on the server and might be returned to you during a + // subsequent receive request. You should ensure that your application is + // idempotent, so that receiving a message more than once does not cause issues. DeleteMessage(ctx context.Context, params *sqs.DeleteMessageInput, optFns ...func(*sqs.Options)) (*sqs.DeleteMessageOutput, error) - // Deletes up to ten messages from the specified queue. This is a batch version of - // DeleteMessage . The result of the action on each message is reported - // individually in the response. Because the batch request can result in a - // combination of successful and unsuccessful actions, you should check for batch - // errors even when the call returns an HTTP status code of 200 . + // Deletes up to ten messages from the specified queue. This is a batch version of DeleteMessage + // . The result of the action on each message is reported individually in the + // response. + // + // Because the batch request can result in a combination of successful and + // unsuccessful actions, you should check for batch errors even when the call + // returns an HTTP status code of 200 . DeleteMessageBatch(ctx context.Context, params *sqs.DeleteMessageBatchInput, optFns ...func(*sqs.Options)) (*sqs.DeleteMessageBatchOutput, error) - // Deletes the queue specified by the QueueUrl , regardless of the queue's - // contents. Be careful with the DeleteQueue action: When you delete a queue, any - // messages in the queue are no longer available. When you delete a queue, the - // deletion process takes up to 60 seconds. Requests you send involving that queue - // during the 60 seconds might succeed. For example, a SendMessage request might - // succeed, but after 60 seconds the queue and the message you sent no longer - // exist. When you delete a queue, you must wait at least 60 seconds before - // creating a queue with the same name. Cross-account permissions don't apply to - // this action. For more information, see Grant cross-account permissions to a - // role and a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) - // in the Amazon SQS Developer Guide. The delete operation uses the HTTP GET verb. + // Deletes the queue specified by the QueueUrl , regardless of the queue's contents. + // + // Be careful with the DeleteQueue action: When you delete a queue, any messages + // in the queue are no longer available. + // + // When you delete a queue, the deletion process takes up to 60 seconds. Requests + // you send involving that queue during the 60 seconds might succeed. For example, + // a SendMessagerequest might succeed, but after 60 seconds the queue and the message you + // sent no longer exist. + // + // When you delete a queue, you must wait at least 60 seconds before creating a + // queue with the same name. + // + // Cross-account permissions don't apply to this action. For more information, see [Grant cross-account permissions to a role and a username] + // in the Amazon SQS Developer Guide. + // + // The delete operation uses the HTTP GET verb. + // + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name DeleteQueue(ctx context.Context, params *sqs.DeleteQueueInput, optFns ...func(*sqs.Options)) (*sqs.DeleteQueueOutput, error) - // Gets attributes for the specified queue. To determine whether a queue is FIFO (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html) - // , you can check whether QueueName ends with the .fifo suffix. + // Gets attributes for the specified queue. + // + // To determine whether a queue is [FIFO], you can check whether QueueName ends with the + // .fifo suffix. + // + // [FIFO]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html GetQueueAttributes(ctx context.Context, params *sqs.GetQueueAttributesInput, optFns ...func(*sqs.Options)) (*sqs.GetQueueAttributesOutput, error) - // Returns the URL of an existing Amazon SQS queue. To access a queue that belongs - // to another AWS account, use the QueueOwnerAWSAccountId parameter to specify the - // account ID of the queue's owner. The queue's owner must grant you permission to - // access the queue. For more information about shared queue access, see - // AddPermission or see Allow Developers to Write Messages to a Shared Queue (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-writing-an-sqs-policy.html#write-messages-to-shared-queue) - // in the Amazon SQS Developer Guide. + // Returns the URL of an existing Amazon SQS queue. + // + // To access a queue that belongs to another AWS account, use the + // QueueOwnerAWSAccountId parameter to specify the account ID of the queue's owner. + // The queue's owner must grant you permission to access the queue. For more + // information about shared queue access, see AddPermissionor see [Allow Developers to Write Messages to a Shared Queue] in the Amazon SQS Developer + // Guide. + // + // [Allow Developers to Write Messages to a Shared Queue]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-writing-an-sqs-policy.html#write-messages-to-shared-queue GetQueueUrl(ctx context.Context, params *sqs.GetQueueUrlInput, optFns ...func(*sqs.Options)) (*sqs.GetQueueUrlOutput, error) // Returns a list of your queues that have the RedrivePolicy queue attribute - // configured with a dead-letter queue. The ListDeadLetterSourceQueues methods - // supports pagination. Set parameter MaxResults in the request to specify the - // maximum number of results to be returned in the response. If you do not set - // MaxResults , the response includes a maximum of 1,000 results. If you set - // MaxResults and there are additional results to display, the response includes a - // value for NextToken . Use NextToken as a parameter in your next request to - // ListDeadLetterSourceQueues to receive the next page of results. For more - // information about using dead-letter queues, see Using Amazon SQS Dead-Letter - // Queues (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html) - // in the Amazon SQS Developer Guide. + // configured with a dead-letter queue. + // + // The ListDeadLetterSourceQueues methods supports pagination. Set parameter + // MaxResults in the request to specify the maximum number of results to be + // returned in the response. If you do not set MaxResults , the response includes a + // maximum of 1,000 results. If you set MaxResults and there are additional + // results to display, the response includes a value for NextToken . Use NextToken + // as a parameter in your next request to ListDeadLetterSourceQueues to receive + // the next page of results. + // + // For more information about using dead-letter queues, see [Using Amazon SQS Dead-Letter Queues] in the Amazon SQS + // Developer Guide. + // + // [Using Amazon SQS Dead-Letter Queues]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html ListDeadLetterSourceQueues(ctx context.Context, params *sqs.ListDeadLetterSourceQueuesInput, optFns ...func(*sqs.Options)) (*sqs.ListDeadLetterSourceQueuesOutput, error) // Gets the most recent message movement tasks (up to 10) under a specific source // queue. - // - This action is currently limited to supporting message redrive from - // dead-letter queues (DLQs) (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html) - // only. In this context, the source queue is the dead-letter queue (DLQ), while - // the destination queue can be the original source queue (from which the messages - // were driven to the dead-letter-queue), or a custom destination queue. - // - Currently, only standard queues are supported. + // + // - This action is currently limited to supporting message redrive from [dead-letter queues (DLQs)]only. + // In this context, the source queue is the dead-letter queue (DLQ), while the + // destination queue can be the original source queue (from which the messages were + // driven to the dead-letter-queue), or a custom destination queue. + // // - Only one active message movement task is supported per queue at any given // time. + // + // [dead-letter queues (DLQs)]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html ListMessageMoveTasks(ctx context.Context, params *sqs.ListMessageMoveTasksInput, optFns ...func(*sqs.Options)) (*sqs.ListMessageMoveTasksOutput, error) // List all cost allocation tags added to the specified Amazon SQS queue. For an - // overview, see Tagging Your Amazon SQS Queues (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html) - // in the Amazon SQS Developer Guide. Cross-account permissions don't apply to this - // action. For more information, see Grant cross-account permissions to a role and - // a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) + // overview, see [Tagging Your Amazon SQS Queues]in the Amazon SQS Developer Guide. + // + // Cross-account permissions don't apply to this action. For more information, see [Grant cross-account permissions to a role and a username] // in the Amazon SQS Developer Guide. + // + // [Tagging Your Amazon SQS Queues]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name ListQueueTags(ctx context.Context, params *sqs.ListQueueTagsInput, optFns ...func(*sqs.Options)) (*sqs.ListQueueTagsOutput, error) // Returns a list of your queues in the current region. The response includes a // maximum of 1,000 results. If you specify a value for the optional // QueueNamePrefix parameter, only queues with a name that begins with the - // specified value are returned. The listQueues methods supports pagination. Set - // parameter MaxResults in the request to specify the maximum number of results to - // be returned in the response. If you do not set MaxResults , the response - // includes a maximum of 1,000 results. If you set MaxResults and there are - // additional results to display, the response includes a value for NextToken . Use - // NextToken as a parameter in your next request to listQueues to receive the next - // page of results. Cross-account permissions don't apply to this action. For more - // information, see Grant cross-account permissions to a role and a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) + // specified value are returned. + // + // The listQueues methods supports pagination. Set parameter MaxResults in the + // request to specify the maximum number of results to be returned in the response. + // If you do not set MaxResults , the response includes a maximum of 1,000 results. + // If you set MaxResults and there are additional results to display, the response + // includes a value for NextToken . Use NextToken as a parameter in your next + // request to listQueues to receive the next page of results. + // + // Cross-account permissions don't apply to this action. For more information, see [Grant cross-account permissions to a role and a username] // in the Amazon SQS Developer Guide. + // + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name ListQueues(ctx context.Context, params *sqs.ListQueuesInput, optFns ...func(*sqs.Options)) (*sqs.ListQueuesOutput, error) // Deletes available messages in a queue (including in-flight messages) specified - // by the QueueURL parameter. When you use the PurgeQueue action, you can't - // retrieve any messages deleted from a queue. The message deletion process takes - // up to 60 seconds. We recommend waiting for 60 seconds regardless of your queue's - // size. Messages sent to the queue before you call PurgeQueue might be received - // but are deleted within the next minute. Messages sent to the queue after you - // call PurgeQueue might be deleted while the queue is being purged. + // by the QueueURL parameter. + // + // When you use the PurgeQueue action, you can't retrieve any messages deleted + // from a queue. + // + // The message deletion process takes up to 60 seconds. We recommend waiting for + // 60 seconds regardless of your queue's size. + // + // Messages sent to the queue before you call PurgeQueue might be received but are + // deleted within the next minute. + // + // Messages sent to the queue after you call PurgeQueue might be deleted while the + // queue is being purged. PurgeQueue(ctx context.Context, params *sqs.PurgeQueueInput, optFns ...func(*sqs.Options)) (*sqs.PurgeQueueOutput, error) // Retrieves one or more messages (up to 10), from the specified queue. Using the - // WaitTimeSeconds parameter enables long-poll support. For more information, see - // Amazon SQS Long Polling (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-long-polling.html) - // in the Amazon SQS Developer Guide. Short poll is the default behavior where a - // weighted random set of machines is sampled on a ReceiveMessage call. Thus, only - // the messages on the sampled machines are returned. If the number of messages in - // the queue is small (fewer than 1,000), you most likely get fewer messages than - // you requested per ReceiveMessage call. If the number of messages in the queue - // is extremely small, you might not receive any messages in a particular - // ReceiveMessage response. If this happens, repeat the request. For each message - // returned, the response includes the following: + // WaitTimeSeconds parameter enables long-poll support. For more information, see [Amazon SQS Long Polling] + // in the Amazon SQS Developer Guide. + // + // Short poll is the default behavior where a weighted random set of machines is + // sampled on a ReceiveMessage call. Thus, only the messages on the sampled + // machines are returned. If the number of messages in the queue is small (fewer + // than 1,000), you most likely get fewer messages than you requested per + // ReceiveMessage call. If the number of messages in the queue is extremely small, + // you might not receive any messages in a particular ReceiveMessage response. If + // this happens, repeat the request. + // + // For each message returned, the response includes the following: + // // - The message body. - // - An MD5 digest of the message body. For information about MD5, see RFC1321 (https://www.ietf.org/rfc/rfc1321.txt) - // . + // + // - An MD5 digest of the message body. For information about MD5, see [RFC1321]. + // // - The MessageId you received when you sent the message to the queue. + // // - The receipt handle. + // // - The message attributes. + // // - An MD5 digest of the message attributes. // // The receipt handle is the identifier you must provide when deleting the - // message. For more information, see Queue and Message Identifiers (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-message-identifiers.html) - // in the Amazon SQS Developer Guide. You can provide the VisibilityTimeout - // parameter in your request. The parameter is applied to the messages that Amazon - // SQS returns in the response. If you don't include the parameter, the overall - // visibility timeout for the queue is used for the returned messages. For more - // information, see Visibility Timeout (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html) - // in the Amazon SQS Developer Guide. A message that isn't deleted or a message - // whose visibility isn't extended before the visibility timeout expires counts as - // a failed receive. Depending on the configuration of the queue, the message might - // be sent to the dead-letter queue. In the future, new attributes might be added. - // If you write code that calls this action, we recommend that you structure your - // code so that it can handle new attributes gracefully. + // message. For more information, see [Queue and Message Identifiers]in the Amazon SQS Developer Guide. + // + // You can provide the VisibilityTimeout parameter in your request. The parameter + // is applied to the messages that Amazon SQS returns in the response. If you don't + // include the parameter, the overall visibility timeout for the queue is used for + // the returned messages. For more information, see [Visibility Timeout]in the Amazon SQS Developer + // Guide. + // + // A message that isn't deleted or a message whose visibility isn't extended + // before the visibility timeout expires counts as a failed receive. Depending on + // the configuration of the queue, the message might be sent to the dead-letter + // queue. + // + // In the future, new attributes might be added. If you write code that calls this + // action, we recommend that you structure your code so that it can handle new + // attributes gracefully. + // + // [Queue and Message Identifiers]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-message-identifiers.html + // [Visibility Timeout]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html + // [Amazon SQS Long Polling]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-long-polling.html + // [RFC1321]: https://www.ietf.org/rfc/rfc1321.txt ReceiveMessage(ctx context.Context, params *sqs.ReceiveMessageInput, optFns ...func(*sqs.Options)) (*sqs.ReceiveMessageOutput, error) // Revokes any permissions in the queue policy that matches the specified Label // parameter. + // // - Only the owner of a queue can remove permissions from it. + // // - Cross-account permissions don't apply to this action. For more information, - // see Grant cross-account permissions to a role and a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) - // in the Amazon SQS Developer Guide. + // see [Grant cross-account permissions to a role and a username]in the Amazon SQS Developer Guide. + // // - To remove the ability to change queue permissions, you must deny permission // to the AddPermission , RemovePermission , and SetQueueAttributes actions in // your IAM policy. + // + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name RemovePermission(ctx context.Context, params *sqs.RemovePermissionInput, optFns ...func(*sqs.Options)) (*sqs.RemovePermissionOutput, error) - // Delivers a message to the specified queue. A message can include only XML, - // JSON, and unformatted text. The following Unicode characters are allowed: #x9 | - // #xA | #xD | #x20 to #xD7FF | #xE000 to #xFFFD | #x10000 to #x10FFFF Any - // characters not included in this list will be rejected. For more information, see - // the W3C specification for characters (http://www.w3.org/TR/REC-xml/#charsets) . + // Delivers a message to the specified queue. + // + // A message can include only XML, JSON, and unformatted text. The following + // Unicode characters are allowed: + // + // #x9 | #xA | #xD | #x20 to #xD7FF | #xE000 to #xFFFD | #x10000 to #x10FFFF + // + // Any characters not included in this list will be rejected. For more + // information, see the [W3C specification for characters]. + // + // [W3C specification for characters]: http://www.w3.org/TR/REC-xml/#charsets SendMessage(ctx context.Context, params *sqs.SendMessageInput, optFns ...func(*sqs.Options)) (*sqs.SendMessageOutput, error) // You can use SendMessageBatch to send up to 10 messages to the specified queue // by assigning either identical or different values to each message (or by not - // assigning values at all). This is a batch version of SendMessage . For a FIFO - // queue, multiple messages within a single batch are enqueued in the order they - // are sent. The result of sending each message is reported individually in the - // response. Because the batch request can result in a combination of successful - // and unsuccessful actions, you should check for batch errors even when the call - // returns an HTTP status code of 200 . The maximum allowed individual message size - // and the maximum total payload size (the sum of the individual lengths of all of - // the batched messages) are both 256 KiB (262,144 bytes). A message can include - // only XML, JSON, and unformatted text. The following Unicode characters are - // allowed: #x9 | #xA | #xD | #x20 to #xD7FF | #xE000 to #xFFFD | #x10000 to - // #x10FFFF Any characters not included in this list will be rejected. For more - // information, see the W3C specification for characters (http://www.w3.org/TR/REC-xml/#charsets) - // . If you don't specify the DelaySeconds parameter for an entry, Amazon SQS uses + // assigning values at all). This is a batch version of SendMessage. For a FIFO queue, + // multiple messages within a single batch are enqueued in the order they are sent. + // + // The result of sending each message is reported individually in the response. + // Because the batch request can result in a combination of successful and + // unsuccessful actions, you should check for batch errors even when the call + // returns an HTTP status code of 200 . + // + // The maximum allowed individual message size and the maximum total payload size + // (the sum of the individual lengths of all of the batched messages) are both 256 + // KiB (262,144 bytes). + // + // A message can include only XML, JSON, and unformatted text. The following + // Unicode characters are allowed: + // + // #x9 | #xA | #xD | #x20 to #xD7FF | #xE000 to #xFFFD | #x10000 to #x10FFFF + // + // Any characters not included in this list will be rejected. For more + // information, see the [W3C specification for characters]. + // + // If you don't specify the DelaySeconds parameter for an entry, Amazon SQS uses // the default value for the queue. + // + // [W3C specification for characters]: http://www.w3.org/TR/REC-xml/#charsets SendMessageBatch(ctx context.Context, params *sqs.SendMessageBatchInput, optFns ...func(*sqs.Options)) (*sqs.SendMessageBatchOutput, error) - // Sets the value of one or more queue attributes. When you change a queue's - // attributes, the change can take up to 60 seconds for most of the attributes to - // propagate throughout the Amazon SQS system. Changes made to the + // Sets the value of one or more queue attributes, like a policy. When you change + // a queue's attributes, the change can take up to 60 seconds for most of the + // attributes to propagate throughout the Amazon SQS system. Changes made to the // MessageRetentionPeriod attribute can take up to 15 minutes and will impact // existing messages in the queue potentially causing them to be expired and // deleted if the MessageRetentionPeriod is reduced below the age of existing // messages. + // // - In the future, new attributes might be added. If you write code that calls // this action, we recommend that you structure your code so that it can handle new // attributes gracefully. + // // - Cross-account permissions don't apply to this action. For more information, - // see Grant cross-account permissions to a role and a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) - // in the Amazon SQS Developer Guide. + // see [Grant cross-account permissions to a role and a username]in the Amazon SQS Developer Guide. + // // - To remove the ability to change queue permissions, you must deny permission // to the AddPermission , RemovePermission , and SetQueueAttributes actions in // your IAM policy. + // + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name SetQueueAttributes(ctx context.Context, params *sqs.SetQueueAttributesInput, optFns ...func(*sqs.Options)) (*sqs.SetQueueAttributesOutput, error) // Starts an asynchronous task to move messages from a specified source queue to a // specified destination queue. + // // - This action is currently limited to supporting message redrive from queues - // that are configured as dead-letter queues (DLQs) (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html) - // of other Amazon SQS queues only. Non-SQS queue sources of dead-letter queues, - // such as Lambda or Amazon SNS topics, are currently not supported. + // that are configured as [dead-letter queues (DLQs)]of other Amazon SQS queues only. Non-SQS queue sources + // of dead-letter queues, such as Lambda or Amazon SNS topics, are currently not + // supported. + // // - In dead-letter queues redrive context, the StartMessageMoveTask the source // queue is the DLQ, while the destination queue can be the original source queue // (from which the messages were driven to the dead-letter-queue), or a custom // destination queue. - // - Currently, only standard queues support redrive. FIFO queues don't support - // redrive. + // // - Only one active message movement task is supported per queue at any given // time. + // + // [dead-letter queues (DLQs)]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html StartMessageMoveTask(ctx context.Context, params *sqs.StartMessageMoveTaskInput, optFns ...func(*sqs.Options)) (*sqs.StartMessageMoveTaskOutput, error) // Add cost allocation tags to the specified Amazon SQS queue. For an overview, - // see Tagging Your Amazon SQS Queues (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html) - // in the Amazon SQS Developer Guide. When you use queue tags, keep the following - // guidelines in mind: + // see [Tagging Your Amazon SQS Queues]in the Amazon SQS Developer Guide. + // + // When you use queue tags, keep the following guidelines in mind: + // // - Adding more than 50 tags to a queue isn't recommended. + // // - Tags don't have any semantic meaning. Amazon SQS interprets tags as // character strings. + // // - Tags are case-sensitive. + // // - A new tag with a key identical to that of an existing tag overwrites the // existing tag. // - // For a full list of tag restrictions, see Quotas related to queues (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-limits.html#limits-queues) - // in the Amazon SQS Developer Guide. Cross-account permissions don't apply to this - // action. For more information, see Grant cross-account permissions to a role and - // a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) + // For a full list of tag restrictions, see [Quotas related to queues] in the Amazon SQS Developer Guide. + // + // Cross-account permissions don't apply to this action. For more information, see [Grant cross-account permissions to a role and a username] // in the Amazon SQS Developer Guide. + // + // [Tagging Your Amazon SQS Queues]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html + // [Quotas related to queues]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-limits.html#limits-queues + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name TagQueue(ctx context.Context, params *sqs.TagQueueInput, optFns ...func(*sqs.Options)) (*sqs.TagQueueOutput, error) // Remove cost allocation tags from the specified Amazon SQS queue. For an - // overview, see Tagging Your Amazon SQS Queues (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html) - // in the Amazon SQS Developer Guide. Cross-account permissions don't apply to this - // action. For more information, see Grant cross-account permissions to a role and - // a username (https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name) + // overview, see [Tagging Your Amazon SQS Queues]in the Amazon SQS Developer Guide. + // + // Cross-account permissions don't apply to this action. For more information, see [Grant cross-account permissions to a role and a username] // in the Amazon SQS Developer Guide. + // + // [Tagging Your Amazon SQS Queues]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html + // [Grant cross-account permissions to a role and a username]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name UntagQueue(ctx context.Context, params *sqs.UntagQueueInput, optFns ...func(*sqs.Options)) (*sqs.UntagQueueOutput, error) }