Add retryMode ALL_ACTIONS to RetryStageExecution API that retries a f…

…ailed stage starting from first action in the stage

Add domainWithSuffix finding field to dnsRequestAction
Fixed error where ListCustomRoutingEndpointGroups did not have a paginator
Documentation only updates to address Amazon ECS tickets.
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.
This release introduces three new APIs: StartBatchDeleteConfigurationTask, DescribeBatchDeleteConfigurationTask, and BatchDeleteAgents.
Adds permissions for GetResourcePolicy to support returning details about AWS Resource Access Manager resource policies for shared resources.
Adds Owner field to ListRoutingControls API.

VERSION

@@ -1 +1 @@
-1.11.180
+1.11.181

generated/src/aws-cpp-sdk-codepipeline/include/aws/codepipeline/CodePipelineClient.h

@@ -1033,10 +1033,15 @@ namespace CodePipeline
         }
 
         /**
-         * <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><p><h3>See Also:</h3>   <a
+         * <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><p><h3>See
+         * Also:</h3>   <a
          * href="http://docs.aws.amazon.com/goto/WebAPI/codepipeline-2015-07-09/RetryStageExecution">AWS
          * API Reference</a></p>
          */

generated/src/aws-cpp-sdk-codepipeline/include/aws/codepipeline/model/RetryStageExecutionRequest.h

@@ -179,38 +179,32 @@ namespace Model
 
 
     /**
-     * <p>The scope of the retry attempt. Currently, the only supported value is
-     * FAILED_ACTIONS.</p>
+     * <p>The scope of the retry attempt.</p>
      */
     inline const StageRetryMode& GetRetryMode() const{ return m_retryMode; }
 
     /**
-     * <p>The scope of the retry attempt. Currently, the only supported value is
-     * FAILED_ACTIONS.</p>
+     * <p>The scope of the retry attempt.</p>
      */
     inline bool RetryModeHasBeenSet() const { return m_retryModeHasBeenSet; }
 
     /**
-     * <p>The scope of the retry attempt. Currently, the only supported value is
-     * FAILED_ACTIONS.</p>
+     * <p>The scope of the retry attempt.</p>
      */
     inline void SetRetryMode(const StageRetryMode& value) { m_retryModeHasBeenSet = true; m_retryMode = value; }
 
     /**
-     * <p>The scope of the retry attempt. Currently, the only supported value is
-     * FAILED_ACTIONS.</p>
+     * <p>The scope of the retry attempt.</p>
      */
     inline void SetRetryMode(StageRetryMode&& value) { m_retryModeHasBeenSet = true; m_retryMode = std::move(value); }
 
     /**
-     * <p>The scope of the retry attempt. Currently, the only supported value is
-     * FAILED_ACTIONS.</p>
+     * <p>The scope of the retry attempt.</p>
      */
     inline RetryStageExecutionRequest& WithRetryMode(const StageRetryMode& value) { SetRetryMode(value); return *this;}
 
     /**
-     * <p>The scope of the retry attempt. Currently, the only supported value is
-     * FAILED_ACTIONS.</p>
+     * <p>The scope of the retry attempt.</p>
      */
     inline RetryStageExecutionRequest& WithRetryMode(StageRetryMode&& value) { SetRetryMode(std::move(value)); return *this;}
 

generated/src/aws-cpp-sdk-codepipeline/include/aws/codepipeline/model/StageRetryMode.h

@@ -16,7 +16,8 @@ namespace Model
   enum class StageRetryMode
   {
     NOT_SET,
-    FAILED_ACTIONS
+    FAILED_ACTIONS,
+    ALL_ACTIONS
   };
 
 namespace StageRetryModeMapper

generated/src/aws-cpp-sdk-codepipeline/source/model/StageRetryMode.cpp

@@ -21,6 +21,7 @@ namespace Aws
       {
 
         static const int FAILED_ACTIONS_HASH = HashingUtils::HashString("FAILED_ACTIONS");
+        static const int ALL_ACTIONS_HASH = HashingUtils::HashString("ALL_ACTIONS");
 
 
         StageRetryMode GetStageRetryModeForName(const Aws::String& name)
@@ -30,6 +31,10 @@ namespace Aws
           {
             return StageRetryMode::FAILED_ACTIONS;
           }
+          else if (hashCode == ALL_ACTIONS_HASH)
+          {
+            return StageRetryMode::ALL_ACTIONS;
+          }
           EnumParseOverflowContainer* overflowContainer = Aws::GetEnumOverflowContainer();
           if(overflowContainer)
           {
@@ -48,6 +53,8 @@ namespace Aws
             return {};
           case StageRetryMode::FAILED_ACTIONS:
             return "FAILED_ACTIONS";
+          case StageRetryMode::ALL_ACTIONS:
+            return "ALL_ACTIONS";
           default:
             EnumParseOverflowContainer* overflowContainer = Aws::GetEnumOverflowContainer();
             if(overflowContainer)

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/model/ClusterServiceConnectDefaultsRequest.h

@@ -64,7 +64,7 @@ namespace Model
      * Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance
      * discovery only. This instance discovery method is the "HTTP" namespace type in
      * the Command Line Interface. Other types of instance discovery aren't used by
-     * Service Connect.</p> <p>If you update the service with an empty string
+     * Service Connect.</p> <p>If you update the cluster with an empty string
      * <code>""</code> for the namespace name, the cluster configuration for Service
      * Connect is removed. Note that the namespace will remain in Cloud Map and must be
      * deleted separately.</p> <p>For more information about Cloud Map, see <a
@@ -85,7 +85,7 @@ namespace Model
      * Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance
      * discovery only. This instance discovery method is the "HTTP" namespace type in
      * the Command Line Interface. Other types of instance discovery aren't used by
-     * Service Connect.</p> <p>If you update the service with an empty string
+     * Service Connect.</p> <p>If you update the cluster with an empty string
      * <code>""</code> for the namespace name, the cluster configuration for Service
      * Connect is removed. Note that the namespace will remain in Cloud Map and must be
      * deleted separately.</p> <p>For more information about Cloud Map, see <a
@@ -106,7 +106,7 @@ namespace Model
      * Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance
      * discovery only. This instance discovery method is the "HTTP" namespace type in
      * the Command Line Interface. Other types of instance discovery aren't used by
-     * Service Connect.</p> <p>If you update the service with an empty string
+     * Service Connect.</p> <p>If you update the cluster with an empty string
      * <code>""</code> for the namespace name, the cluster configuration for Service
      * Connect is removed. Note that the namespace will remain in Cloud Map and must be
      * deleted separately.</p> <p>For more information about Cloud Map, see <a
@@ -127,7 +127,7 @@ namespace Model
      * Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance
      * discovery only. This instance discovery method is the "HTTP" namespace type in
      * the Command Line Interface. Other types of instance discovery aren't used by
-     * Service Connect.</p> <p>If you update the service with an empty string
+     * Service Connect.</p> <p>If you update the cluster with an empty string
      * <code>""</code> for the namespace name, the cluster configuration for Service
      * Connect is removed. Note that the namespace will remain in Cloud Map and must be
      * deleted separately.</p> <p>For more information about Cloud Map, see <a
@@ -148,7 +148,7 @@ namespace Model
      * Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance
      * discovery only. This instance discovery method is the "HTTP" namespace type in
      * the Command Line Interface. Other types of instance discovery aren't used by
-     * Service Connect.</p> <p>If you update the service with an empty string
+     * Service Connect.</p> <p>If you update the cluster with an empty string
      * <code>""</code> for the namespace name, the cluster configuration for Service
      * Connect is removed. Note that the namespace will remain in Cloud Map and must be
      * deleted separately.</p> <p>For more information about Cloud Map, see <a
@@ -169,7 +169,7 @@ namespace Model
      * Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance
      * discovery only. This instance discovery method is the "HTTP" namespace type in
      * the Command Line Interface. Other types of instance discovery aren't used by
-     * Service Connect.</p> <p>If you update the service with an empty string
+     * Service Connect.</p> <p>If you update the cluster with an empty string
      * <code>""</code> for the namespace name, the cluster configuration for Service
      * Connect is removed. Note that the namespace will remain in Cloud Map and must be
      * deleted separately.</p> <p>For more information about Cloud Map, see <a
@@ -190,7 +190,7 @@ namespace Model
      * Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance
      * discovery only. This instance discovery method is the "HTTP" namespace type in
      * the Command Line Interface. Other types of instance discovery aren't used by
-     * Service Connect.</p> <p>If you update the service with an empty string
+     * Service Connect.</p> <p>If you update the cluster with an empty string
      * <code>""</code> for the namespace name, the cluster configuration for Service
      * Connect is removed. Note that the namespace will remain in Cloud Map and must be
      * deleted separately.</p> <p>For more information about Cloud Map, see <a
@@ -211,7 +211,7 @@ namespace Model
      * Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance
      * discovery only. This instance discovery method is the "HTTP" namespace type in
      * the Command Line Interface. Other types of instance discovery aren't used by
-     * Service Connect.</p> <p>If you update the service with an empty string
+     * Service Connect.</p> <p>If you update the cluster with an empty string
      * <code>""</code> for the namespace name, the cluster configuration for Service
      * Connect is removed. Note that the namespace will remain in Cloud Map and must be
      * deleted separately.</p> <p>For more information about Cloud Map, see <a

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/model/EnvironmentFile.h

@@ -29,20 +29,21 @@ namespace Model
    * You can specify up to ten environment files. The file must have a
    * <code>.env</code> file extension. Each line in an environment file should
    * contain an environment variable in <code>VARIABLE=VALUE</code> format. Lines
-   * beginning with <code>#</code> are treated as comments and are ignored. For more
-   * information about the environment variable file syntax, see <a
-   * href="https://docs.docker.com/compose/env-file/">Declare default environment
-   * variables in file</a>.</p> <p>If there are environment variables specified using
-   * the <code>environment</code> parameter in a container definition, they take
-   * precedence over the variables contained within an environment file. If multiple
-   * environment files are specified that contain the same variable, they're
-   * processed from the top down. We recommend that you use unique variable names.
-   * For more information, see <a
+   * beginning with <code>#</code> are treated as comments and are ignored.</p> <p>If
+   * there are environment variables specified using the <code>environment</code>
+   * parameter in a container definition, they take precedence over the variables
+   * contained within an environment file. If multiple environment files are
+   * specified that contain the same variable, they're processed from the top down.
+   * We recommend that you use unique variable names. For more information, see <a
    * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/taskdef-envfiles.html">Specifying
    * environment variables</a> in the <i>Amazon Elastic Container Service Developer
    * Guide</i>.</p> <p>You must use the following platforms for the Fargate launch
    * type:</p> <ul> <li> <p>Linux platform version <code>1.4.0</code> or later.</p>
    * </li> <li> <p>Windows platform version <code>1.0.0</code> or later.</p> </li>
+   * </ul> <p>Consider the following when using the Fargate launch type:</p> <ul>
+   * <li> <p>The file is handled like a native Docker env-file.</p> </li> <li>
+   * <p>There is no support for shell escape handling.</p> </li> <li> <p>The
+   * container entry point interperts the <code>VARIABLE</code> values.</p> </li>
    * </ul><p><h3>See Also:</h3>   <a
    * href="http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/EnvironmentFile">AWS
    * API Reference</a></p>

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/model/HealthCheck.h

@@ -44,27 +44,51 @@ namespace Model
    * <code>HEALTHY</code>-The container health check has passed successfully.</p>
    * </li> <li> <p> <code>UNHEALTHY</code>-The container health check has failed.</p>
    * </li> <li> <p> <code>UNKNOWN</code>-The container health check is being
-   * evaluated or there's no container health check defined.</p> </li> </ul> <p>The
-   * following describes the possible <code>healthStatus</code> values for a task.
-   * The container health check status of non-essential containers don't have an
-   * effect on the health status of a task.</p> <ul> <li> <p>
-   * <code>HEALTHY</code>-All essential containers within the task have passed their
-   * health checks.</p> </li> <li> <p> <code>UNHEALTHY</code>-One or more essential
-   * containers have failed their health check.</p> </li> <li> <p>
-   * <code>UNKNOWN</code>-The essential containers within the task are still having
-   * their health checks evaluated, there are only nonessential containers with
-   * health checks defined, or there are no container health checks defined.</p>
-   * </li> </ul> <p>If a task is run manually, and not as part of a service, the task
-   * will continue its lifecycle regardless of its health status. For tasks that are
-   * part of a service, if the task reports as unhealthy then the task will be
-   * stopped and the service scheduler will replace it.</p> <p>The following are
-   * notes about container health check support:</p> <ul> <li> <p>When the Amazon ECS
-   * agent cannot connect to the Amazon ECS service, the service reports the
-   * container as <code>UNHEALTHY</code>. </p> </li> <li> <p>The health check
-   * statuses are the "last heard from" response from the Amazon ECS agent. There are
-   * no assumptions made about the status of the container health checks.</p> </li>
-   * <li> <p>Container health checks require version 1.17.0 or greater of the Amazon
-   * ECS container agent. For more information, see <a
+   * evaluated, there's no container health check defined, or Amazon ECS doesn't have
+   * the health status of the container.</p> </li> </ul> <p>The following describes
+   * the possible <code>healthStatus</code> values based on the container health
+   * checker status of essential containers in the task with the following priority
+   * order (high to low):</p> <ul> <li> <p> <code>UNHEALTHY</code>-One or more
+   * essential containers have failed their health check.</p> </li> <li> <p>
+   * <code>UNKNOWN</code>-Any essential container running within the task is in an
+   * <code>UNKNOWN</code> state and no other essential containers have an
+   * <code>UNHEALTHY</code> state.</p> </li> <li> <p> <code>HEALTHY</code>-All
+   * essential containers within the task have passed their health checks.</p> </li>
+   * </ul> <p>Consider the following task health example with 2 containers.</p> <ul>
+   * <li> <p>If Container1 is <code>UNHEALTHY</code> and Container2 is
+   * <code>UNKNOWN</code>, the task health is <code>UNHEALTHY</code>.</p> </li> <li>
+   * <p>If Container1 is <code>UNHEALTHY</code> and Container2 is
+   * <code>HEALTHY</code>, the task health is <code>UNHEALTHY</code>.</p> </li> <li>
+   * <p>If Container1 is <code>HEALTHY</code> and Container2 is <code>UNKNOWN</code>,
+   * the task health is <code>UNKNOWN</code>.</p> </li> <li> <p>If Container1 is
+   * <code>HEALTHY</code> and Container2 is <code>HEALTHY</code>, the task health is
+   * <code>HEALTHY</code>.</p> </li> </ul> <p>Consider the following task health
+   * example with 3 containers.</p> <ul> <li> <p>If Container1 is
+   * <code>UNHEALTHY</code> and Container2 is <code>UNKNOWN</code>, and Container3 is
+   * <code>UNKNOWN</code>, the task health is <code>UNHEALTHY</code>.</p> </li> <li>
+   * <p>If Container1 is <code>UNHEALTHY</code> and Container2 is
+   * <code>UNKNOWN</code>, and Container3 is <code>HEALTHY</code>, the task health is
+   * <code>UNHEALTHY</code>.</p> </li> <li> <p>If Container1 is
+   * <code>UNHEALTHY</code> and Container2 is <code>HEALTHY</code>, and Container3 is
+   * <code>HEALTHY</code>, the task health is <code>UNHEALTHY</code>.</p> </li> <li>
+   * <p>If Container1 is <code>HEALTHY</code> and Container2 is <code>UNKNOWN</code>,
+   * and Container3 is <code>HEALTHY</code>, the task health is
+   * <code>UNKNOWN</code>.</p> </li> <li> <p>If Container1 is <code>HEALTHY</code>
+   * and Container2 is <code>UNKNOWN</code>, and Container3 is <code>UNKNOWN</code>,
+   * the task health is <code>UNKNOWN</code>.</p> </li> <li> <p>If Container1 is
+   * <code>HEALTHY</code> and Container2 is <code>HEALTHY</code>, and Container3 is
+   * <code>HEALTHY</code>, the task health is <code>HEALTHY</code>.</p> </li> </ul>
+   * <p>If a task is run manually, and not as part of a service, the task will
+   * continue its lifecycle regardless of its health status. For tasks that are part
+   * of a service, if the task reports as unhealthy then the task will be stopped and
+   * the service scheduler will replace it.</p> <p>The following are notes about
+   * container health check support:</p> <ul> <li> <p>When the Amazon ECS agent
+   * cannot connect to the Amazon ECS service, the service reports the container as
+   * <code>UNHEALTHY</code>. </p> </li> <li> <p>The health check statuses are the
+   * "last heard from" response from the Amazon ECS agent. There are no assumptions
+   * made about the status of the container health checks.</p> </li> <li>
+   * <p>Container health checks require version 1.17.0 or greater of the Amazon ECS
+   * container agent. For more information, see <a
    * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html">Updating
    * the Amazon ECS container agent</a>.</p> </li> <li> <p>Container health checks
    * are supported for Fargate tasks if you're using platform version