Skip to content

Commit

Permalink
Merge branch 'release-1.31.65' into develop
Browse files Browse the repository at this point in the history
* release-1.31.65:
  Bumping version to 1.31.65
  Update to latest partitions and endpoints
  Update to latest models
  • Loading branch information
aws-sdk-python-automation committed Oct 17, 2023
2 parents c099d15 + 04aef3f commit 0682e8a
Show file tree
Hide file tree
Showing 21 changed files with 1,265 additions and 166 deletions.
42 changes: 42 additions & 0 deletions .changes/1.31.65.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
[
{
"category": "``codepipeline``",
"description": "Add retryMode ALL_ACTIONS to RetryStageExecution API that retries a failed stage starting from first action in the stage",
"type": "api-change"
},
{
"category": "``discovery``",
"description": "This release introduces three new APIs: StartBatchDeleteConfigurationTask, DescribeBatchDeleteConfigurationTask, and BatchDeleteAgents.",
"type": "api-change"
},
{
"category": "``ecs``",
"description": "Documentation only updates to address Amazon ECS tickets.",
"type": "api-change"
},
{
"category": "``globalaccelerator``",
"description": "Fixed error where ListCustomRoutingEndpointGroups did not have a paginator",
"type": "api-change"
},
{
"category": "``guardduty``",
"description": "Add domainWithSuffix finding field to dnsRequestAction",
"type": "api-change"
},
{
"category": "``kafka``",
"description": "AWS Managed Streaming for Kafka is launching MSK Replicator, a new feature that enables customers to reliably replicate data across Amazon MSK clusters in same or different AWS regions. You can now use SDK to create, list, describe, delete, update, and manage tags of MSK Replicators.",
"type": "api-change"
},
{
"category": "``route53-recovery-cluster``",
"description": "Adds Owner field to ListRoutingControls API.",
"type": "api-change"
},
{
"category": "``route53-recovery-control-config``",
"description": "Adds permissions for GetResourcePolicy to support returning details about AWS Resource Access Manager resource policies for shared resources.",
"type": "api-change"
}
]
13 changes: 13 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,19 @@
CHANGELOG
=========

1.31.65
=======

* api-change:``codepipeline``: Add retryMode ALL_ACTIONS to RetryStageExecution API that retries a failed stage starting from first action in the stage
* api-change:``discovery``: This release introduces three new APIs: StartBatchDeleteConfigurationTask, DescribeBatchDeleteConfigurationTask, and BatchDeleteAgents.
* api-change:``ecs``: Documentation only updates to address Amazon ECS tickets.
* api-change:``globalaccelerator``: Fixed error where ListCustomRoutingEndpointGroups did not have a paginator
* api-change:``guardduty``: Add domainWithSuffix finding field to dnsRequestAction
* api-change:``kafka``: AWS Managed Streaming for Kafka is launching MSK Replicator, a new feature that enables customers to reliably replicate data across Amazon MSK clusters in same or different AWS regions. You can now use SDK to create, list, describe, delete, update, and manage tags of MSK Replicators.
* api-change:``route53-recovery-cluster``: Adds Owner field to ListRoutingControls API.
* api-change:``route53-recovery-control-config``: Adds permissions for GetResourcePolicy to support returning details about AWS Resource Access Manager resource policies for shared resources.


1.31.64
=======

Expand Down
2 changes: 1 addition & 1 deletion botocore/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
import os
import re

__version__ = '1.31.64'
__version__ = '1.31.65'


class NullHandler(logging.Handler):
Expand Down
40 changes: 20 additions & 20 deletions botocore/data/codepipeline/2015-07-09/endpoint-rule-set-1.json
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand Down Expand Up @@ -83,7 +82,8 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
},
{
"conditions": [
Expand All @@ -96,7 +96,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand All @@ -110,7 +109,6 @@
"assign": "PartitionResult"
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand All @@ -133,7 +131,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand Down Expand Up @@ -168,7 +165,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [],
Expand All @@ -179,14 +175,16 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
},
{
"conditions": [],
"error": "FIPS and DualStack are enabled, but this partition does not support one or both",
"type": "error"
}
]
],
"type": "tree"
},
{
"conditions": [
Expand All @@ -200,14 +198,12 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
{
"fn": "booleanEquals",
"argv": [
true,
{
"fn": "getAttr",
"argv": [
Expand All @@ -216,11 +212,11 @@
},
"supportsFIPS"
]
}
},
true
]
}
],
"type": "tree",
"rules": [
{
"conditions": [],
Expand All @@ -231,14 +227,16 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
},
{
"conditions": [],
"error": "FIPS is enabled but this partition does not support FIPS",
"type": "error"
}
]
],
"type": "tree"
},
{
"conditions": [
Expand All @@ -252,7 +250,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand All @@ -272,7 +269,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [],
Expand All @@ -283,14 +279,16 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
},
{
"conditions": [],
"error": "DualStack is enabled but this partition does not support DualStack",
"type": "error"
}
]
],
"type": "tree"
},
{
"conditions": [],
Expand All @@ -301,9 +299,11 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
}
]
],
"type": "tree"
},
{
"conditions": [],
Expand Down
9 changes: 6 additions & 3 deletions botocore/data/codepipeline/2015-07-09/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -513,7 +513,7 @@
{"shape":"StageNotRetryableException"},
{"shape":"NotLatestPipelineExecutionException"}
],
"documentation":"<p>Resumes the pipeline execution by retrying the last failed actions in a stage. You can retry a stage immediately if any of the actions in the stage fail. When you retry, all actions that are still in progress continue working, and failed actions are triggered again.</p>"
"documentation":"<p>You can retry a stage that has failed without having to run a pipeline again from the beginning. You do this by either retrying the failed actions in a stage or by retrying all actions in the stage starting from the first action in the stage. When you retry the failed actions in a stage, all actions that are still in progress continue working, and failed actions are triggered again. When you retry a failed stage from the first action in the stage, the stage cannot have any actions in progress. Before a stage can be retried, it must either have all actions failed or some actions failed and some succeeded.</p>"
},
"StartPipelineExecution":{
"name":"StartPipelineExecution",
Expand Down Expand Up @@ -3470,7 +3470,7 @@
},
"retryMode":{
"shape":"StageRetryMode",
"documentation":"<p>The scope of the retry attempt. Currently, the only supported value is FAILED_ACTIONS.</p>"
"documentation":"<p>The scope of the retry attempt.</p>"
}
},
"documentation":"<p>Represents the input of a <code>RetryStageExecution</code> action.</p>"
Expand Down Expand Up @@ -3680,7 +3680,10 @@
},
"StageRetryMode":{
"type":"string",
"enum":["FAILED_ACTIONS"]
"enum":[
"FAILED_ACTIONS",
"ALL_ACTIONS"
]
},
"StageState":{
"type":"structure",
Expand Down
Loading

0 comments on commit 0682e8a

Please sign in to comment.