Skip to content

Commit

Permalink
Update services based on v1.44.311 of AWS Go SDK
Browse files Browse the repository at this point in the history
  • Loading branch information
web-flow committed Jul 28, 2023
1 parent 7ab446e commit e095abe
Show file tree
Hide file tree
Showing 4 changed files with 72 additions and 17 deletions.
2 changes: 1 addition & 1 deletion .latest-tag-aws-sdk-go
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v1.44.309
v1.44.311
10 changes: 5 additions & 5 deletions lib/aws/generated/auto_scaling.ex
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ defmodule AWS.AutoScaling do
6. ## If you finish before the timeout period ends, send a callback
by using the `CompleteLifecycleAction` API call.
For more information, see [Amazon EC2 Auto Scaling lifecycle hooks](https://docs.aws.amazon.com/autoscaling/ec2/userguide/lifecycle-hooks.html)
For more information, see [Complete a lifecycle action](https://docs.aws.amazon.com/autoscaling/ec2/userguide/completing-lifecycle-hooks.html)
in the *Amazon EC2 Auto Scaling User Guide*.
"""
def complete_lifecycle_action(%Client{} = client, input, options \\ []) do
Expand Down Expand Up @@ -828,10 +828,10 @@ defmodule AWS.AutoScaling do
@doc """
Detaches one or more traffic sources from the specified Auto Scaling group.
When you detach a taffic, it enters the `Removing` state while deregistering the
instances in the group. When all instances are deregistered, then you can no
longer describe the traffic source using the `DescribeTrafficSources` API call.
The instances continue to run.
When you detach a traffic source, it enters the `Removing` state while
deregistering the instances in the group. When all instances are deregistered,
then you can no longer describe the traffic source using the
`DescribeTrafficSources` API call. The instances continue to run.
"""
def detach_traffic_sources(%Client{} = client, input, options \\ []) do
meta = metadata()
Expand Down
30 changes: 30 additions & 0 deletions lib/aws/generated/ebs.ex
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,11 @@ defmodule AWS.EBS do
Completing the snapshot changes the status to `completed`. You cannot write new
blocks to a snapshot after it has been completed.
You should always retry requests that receive server (`5xx`) error responses,
and `ThrottlingException` and `RequestThrottledException` client error
responses. For more information see [Error retries](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/error-retries.html)
in the *Amazon Elastic Compute Cloud User Guide*.
"""
def complete_snapshot(%Client{} = client, snapshot_id, input, options \\ []) do
url_path = "/snapshots/completion/#{AWS.Util.encode_uri(snapshot_id)}"
Expand Down Expand Up @@ -87,6 +92,11 @@ defmodule AWS.EBS do

@doc """
Returns the data in a block in an Amazon Elastic Block Store snapshot.
You should always retry requests that receive server (`5xx`) error responses,
and `ThrottlingException` and `RequestThrottledException` client error
responses. For more information see [Error retries](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/error-retries.html)
in the *Amazon Elastic Compute Cloud User Guide*.
"""
def get_snapshot_block(%Client{} = client, block_index, snapshot_id, block_token, options \\ []) do
url_path =
Expand Down Expand Up @@ -121,6 +131,11 @@ defmodule AWS.EBS do
@doc """
Returns information about the blocks that are different between two Amazon
Elastic Block Store snapshots of the same volume/snapshot lineage.
You should always retry requests that receive server (`5xx`) error responses,
and `ThrottlingException` and `RequestThrottledException` client error
responses. For more information see [Error retries](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/error-retries.html)
in the *Amazon Elastic Compute Cloud User Guide*.
"""
def list_changed_blocks(
%Client{} = client,
Expand Down Expand Up @@ -170,6 +185,11 @@ defmodule AWS.EBS do

@doc """
Returns information about the blocks in an Amazon Elastic Block Store snapshot.
You should always retry requests that receive server (`5xx`) error responses,
and `ThrottlingException` and `RequestThrottledException` client error
responses. For more information see [Error retries](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/error-retries.html)
in the *Amazon Elastic Compute Cloud User Guide*.
"""
def list_snapshot_blocks(
%Client{} = client,
Expand Down Expand Up @@ -216,6 +236,11 @@ defmodule AWS.EBS do
target snapshot must be in the `pending` state.
Data written to a snapshot must be aligned with 512-KiB sectors.
You should always retry requests that receive server (`5xx`) error responses,
and `ThrottlingException` and `RequestThrottledException` client error
responses. For more information see [Error retries](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/error-retries.html)
in the *Amazon Elastic Compute Cloud User Guide*.
"""
def put_snapshot_block(%Client{} = client, block_index, snapshot_id, input, options \\ []) do
url_path =
Expand Down Expand Up @@ -255,6 +280,11 @@ defmodule AWS.EBS do
After creating the snapshot, use [
PutSnapshotBlock](https://docs.aws.amazon.com/ebs/latest/APIReference/API_PutSnapshotBlock.html)
to write blocks of data to the snapshot.
You should always retry requests that receive server (`5xx`) error responses,
and `ThrottlingException` and `RequestThrottledException` client error
responses. For more information see [Error retries](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/error-retries.html)
in the *Amazon Elastic Compute Cloud User Guide*.
"""
def start_snapshot(%Client{} = client, input, options \\ []) do
url_path = "/snapshots"
Expand Down
47 changes: 36 additions & 11 deletions lib/aws/generated/sqs.ex
Original file line number Diff line number Diff line change
Expand Up @@ -100,12 +100,20 @@ defmodule AWS.SQS do
@doc """
Cancels a specified message movement task.
A message movement can only be cancelled when the current status is
RUNNING.
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.
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.
Only one active message movement task is supported per queue at any
given time.
"""
def cancel_message_move_task(%Client{} = client, input, options \\ []) do
meta = metadata()
Expand Down Expand Up @@ -367,6 +375,17 @@ defmodule AWS.SQS do
@doc """
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.
Only one active message movement task is supported per queue at any
given time.
"""
def list_message_move_tasks(%Client{} = client, input, options \\ []) do
meta = metadata()
Expand Down Expand Up @@ -415,7 +434,8 @@ defmodule AWS.SQS do
end

@doc """
Deletes the messages in a queue specified by the `QueueURL` parameter.
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.
Expand Down Expand Up @@ -595,12 +615,17 @@ defmodule AWS.SQS do
specified destination queue.
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.
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.
Currently, only standard queues are 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.
Expand Down

0 comments on commit e095abe

Please sign in to comment.