Skip to content

Commit 6528881

Browse files
Update to latest models
1 parent 2aaa023 commit 6528881

File tree

13 files changed

+2225
-1479
lines changed

13 files changed

+2225
-1479
lines changed
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"type": "api-change",
3+
"category": "``dynamodb``",
4+
"description": "Doc-only update for DynamoDB. Added information about async behavior for TagResource and UntagResource APIs and updated the description of ResourceInUseException."
5+
}
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"type": "api-change",
3+
"category": "``elbv2``",
4+
"description": "Add paginators for the ELBv2 DescribeListenerCertificates and DescribeRules APIs. Fix broken waiter for the ELBv2 DescribeLoadBalancers API."
5+
}
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"type": "api-change",
3+
"category": "``ivs-realtime``",
4+
"description": "IVS Real-Time now offers customers the ability to broadcast to Stages using RTMP(S)."
5+
}
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"type": "api-change",
3+
"category": "``kafka``",
4+
"description": "Amazon MSK Replicator can now replicate data to identically named topics between MSK clusters within the same AWS Region or across different AWS Regions."
5+
}
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"type": "api-change",
3+
"category": "``sagemaker``",
4+
"description": "Amazon Sagemaker supports orchestrating SageMaker HyperPod clusters with Amazon EKS"
5+
}
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"type": "api-change",
3+
"category": "``sagemaker-runtime``",
4+
"description": "AWS SageMaker Runtime feature: Add sticky routing to support stateful inference models."
5+
}

awscli/botocore/data/dynamodb/2012-08-10/service-2.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -766,7 +766,7 @@
766766
{"shape":"InternalServerError"},
767767
{"shape":"ResourceInUseException"}
768768
],
769-
"documentation":"<p>Associate a set of tags with an Amazon DynamoDB resource. You can then activate these user-defined tags so that they appear on the Billing and Cost Management console for cost allocation tracking. You can call TagResource up to five times per second, per account. </p> <p>For an overview on tagging DynamoDB resources, see <a href=\"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html\">Tagging for DynamoDB</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
769+
"documentation":"<p>Associate a set of tags with an Amazon DynamoDB resource. You can then activate these user-defined tags so that they appear on the Billing and Cost Management console for cost allocation tracking. You can call TagResource up to five times per second, per account. </p> <ul> <li> <p> <code>TagResource</code> is an asynchronous operation. If you issue a <a>ListTagsOfResource</a> request immediately after a <code>TagResource</code> request, DynamoDB might return your previous tag set, if there was one, or an empty tag set. This is because <code>ListTagsOfResource</code> uses an eventually consistent query, and the metadata for your tags or table might not be available at that moment. Wait for a few seconds, and then try the <code>ListTagsOfResource</code> request again.</p> </li> <li> <p>The application or removal of tags using <code>TagResource</code> and <code>UntagResource</code> APIs is eventually consistent. <code>ListTagsOfResource</code> API will only reflect the changes after a few seconds.</p> </li> </ul> <p>For an overview on tagging DynamoDB resources, see <a href=\"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html\">Tagging for DynamoDB</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
770770
"endpointdiscovery":{
771771
}
772772
},
@@ -823,7 +823,7 @@
823823
{"shape":"InternalServerError"},
824824
{"shape":"ResourceInUseException"}
825825
],
826-
"documentation":"<p>Removes the association of tags from an Amazon DynamoDB resource. You can call <code>UntagResource</code> up to five times per second, per account. </p> <p>For an overview on tagging DynamoDB resources, see <a href=\"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html\">Tagging for DynamoDB</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
826+
"documentation":"<p>Removes the association of tags from an Amazon DynamoDB resource. You can call <code>UntagResource</code> up to five times per second, per account. </p> <ul> <li> <p> <code>UntagResource</code> is an asynchronous operation. If you issue a <a>ListTagsOfResource</a> request immediately after an <code>UntagResource</code> request, DynamoDB might return your previous tag set, if there was one, or an empty tag set. This is because <code>ListTagsOfResource</code> uses an eventually consistent query, and the metadata for your tags or table might not be available at that moment. Wait for a few seconds, and then try the <code>ListTagsOfResource</code> request again.</p> </li> <li> <p>The application or removal of tags using <code>TagResource</code> and <code>UntagResource</code> APIs is eventually consistent. <code>ListTagsOfResource</code> API will only reflect the changes after a few seconds.</p> </li> </ul> <p>For an overview on tagging DynamoDB resources, see <a href=\"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html\">Tagging for DynamoDB</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
827827
"endpointdiscovery":{
828828
}
829829
},
@@ -5230,7 +5230,7 @@
52305230
"documentation":"<p>The resource which is being attempted to be changed is in use.</p>"
52315231
}
52325232
},
5233-
"documentation":"<p>The operation conflicts with the resource's availability. For example, you attempted to recreate an existing table, or tried to delete a table currently in the <code>CREATING</code> state.</p>",
5233+
"documentation":"<p>The operation conflicts with the resource's availability. For example:</p> <ul> <li> <p>You attempted to recreate an existing table.</p> </li> <li> <p>You tried to delete a table currently in the <code>CREATING</code> state.</p> </li> <li> <p>You tried to update a resource that was already being updated.</p> </li> </ul> <p>When appropriate, wait for the ongoing update to complete and attempt the request again.</p>",
52345234
"exception":true
52355235
},
52365236
"ResourceNotFoundException":{

awscli/botocore/data/elbv2/2015-12-01/waiters-2.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
},
1414
{
1515
"matcher": "error",
16-
"expected": "LoadBalancerNotFound",
16+
"expected": "LoadBalancerNotFoundException",
1717
"state": "retry"
1818
}
1919
]
@@ -38,7 +38,7 @@
3838
{
3939
"state": "retry",
4040
"matcher": "error",
41-
"expected": "LoadBalancerNotFound"
41+
"expected": "LoadBalancerNotFoundException"
4242
}
4343
]
4444
},
@@ -55,7 +55,7 @@
5555
},
5656
{
5757
"matcher": "error",
58-
"expected": "LoadBalancerNotFound",
58+
"expected": "LoadBalancerNotFoundException",
5959
"state": "success"
6060
}
6161
]

awscli/botocore/data/ivs-realtime/2020-07-14/paginators-1.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,12 @@
55
"output_token": "nextToken",
66
"limit_key": "maxResults",
77
"result_key": "publicKeys"
8+
},
9+
"ListIngestConfigurations": {
10+
"input_token": "nextToken",
11+
"output_token": "nextToken",
12+
"limit_key": "maxResults",
13+
"result_key": "ingestConfigurations"
814
}
915
}
1016
}

0 commit comments

Comments
 (0)