Release v1.45.27 (2023-10-17) (#5025)

Release v1.45.27 (2023-10-17) === ### Service Client Updates * `service/codepipeline`: Updates service API and documentation * Add retryMode ALL_ACTIONS to RetryStageExecution API that retries a failed stage starting from first action in the stage * `service/discovery`: Updates service API and documentation * This release introduces three new APIs: StartBatchDeleteConfigurationTask, DescribeBatchDeleteConfigurationTask, and BatchDeleteAgents. * `service/ecs`: Updates service documentation and examples * Documentation only updates to address Amazon ECS tickets. * `service/globalaccelerator`: Updates service paginators * `service/guardduty`: Updates service API and documentation * Add domainWithSuffix finding field to dnsRequestAction * `service/kafka`: Updates service API, documentation, and paginators * `service/route53-recovery-cluster`: Updates service API and documentation * `service/route53-recovery-control-config`: Updates service API and documentation
aws · Oct 17, 2023 · 1b80db7 · 1b80db7
1 parent 6f2f8e9
commit 1b80db7
Show file tree

Hide file tree

Showing 40 changed files with 5,505 additions and 831 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,20 @@
+Release v1.45.27 (2023-10-17)
+===
+
+### Service Client Updates
+* `service/codepipeline`: Updates service API and documentation
+  * Add retryMode ALL_ACTIONS to RetryStageExecution API that retries a failed stage starting from first action in the stage
+* `service/discovery`: Updates service API and documentation
+  * This release introduces three new APIs: StartBatchDeleteConfigurationTask, DescribeBatchDeleteConfigurationTask, and BatchDeleteAgents.
+* `service/ecs`: Updates service documentation and examples
+  * Documentation only updates to address Amazon ECS tickets.
+* `service/globalaccelerator`: Updates service paginators
+* `service/guardduty`: Updates service API and documentation
+  * Add domainWithSuffix finding field to dnsRequestAction
+* `service/kafka`: Updates service API, documentation, and paginators
+* `service/route53-recovery-cluster`: Updates service API and documentation
+* `service/route53-recovery-control-config`: Updates service API and documentation
+
 Release v1.45.26 (2023-10-16)
 ===
 

diff --git a/aws/endpoints/defaults.go b/aws/endpoints/defaults.go
diff --git a/aws/version.go b/aws/version.go
@@ -5,4 +5,4 @@ package aws
 const SDKName = "aws-sdk-go"
 
 // SDKVersion is the version of this SDK
-const SDKVersion = "1.45.26"
+const SDKVersion = "1.45.27"
diff --git a/models/apis/codepipeline/2015-07-09/api-2.json b/models/apis/codepipeline/2015-07-09/api-2.json
@@ -2466,7 +2466,10 @@
     },
     "StageRetryMode":{
       "type":"string",
-      "enum":["FAILED_ACTIONS"]
+      "enum":[
+        "FAILED_ACTIONS",
+        "ALL_ACTIONS"
+      ]
     },
     "StageState":{
       "type":"structure",

diff --git a/models/apis/codepipeline/2015-07-09/docs-2.json b/models/apis/codepipeline/2015-07-09/docs-2.json
@@ -34,7 +34,7 @@
     "PutThirdPartyJobSuccessResult": "<p>Represents the success of a third party job as returned to the pipeline by a job worker. Used for partner actions only.</p>",
     "PutWebhook": "<p>Defines a webhook and returns a unique webhook URL generated by CodePipeline. This URL can be supplied to third party source hosting providers to call every time there's a code change. When CodePipeline receives a POST request on this URL, the pipeline defined in the webhook is started as long as the POST request satisfied the authentication and filtering requirements supplied when defining the webhook. RegisterWebhookWithThirdParty and DeregisterWebhookWithThirdParty APIs can be used to automatically configure supported third parties to call the generated webhook URL.</p>",
     "RegisterWebhookWithThirdParty": "<p>Configures a connection between the webhook that was created and the external tool with events to be detected.</p>",
-    "RetryStageExecution": "<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>",
+    "RetryStageExecution": "<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": "<p>Starts the specified pipeline. Specifically, it begins processing the latest commit to the source location specified as part of the pipeline.</p>",
     "StopPipelineExecution": "<p>Stops the specified pipeline execution. You choose to either stop the pipeline execution by completing in-progress actions without starting subsequent actions, or by abandoning in-progress actions. While completing or abandoning in-progress actions, the pipeline execution is in a <code>Stopping</code> state. After all in-progress actions are completed or abandoned, the pipeline execution is in a <code>Stopped</code> state.</p>",
     "TagResource": "<p>Adds to or modifies the tags of the given resource. Tags are metadata that can be used to manage a resource. </p>",
@@ -1721,7 +1721,7 @@
     "StageRetryMode": {
       "base": null,
       "refs": {
-        "RetryStageExecutionInput$retryMode": "<p>The scope of the retry attempt. Currently, the only supported value is FAILED_ACTIONS.</p>"
+        "RetryStageExecutionInput$retryMode": "<p>The scope of the retry attempt.</p>"
       }
     },
     "StageState": {