This release removes hookDetails for the Amazon ECS native blue/green deployments.

Author: aws-sdk-cpp-automation

VERSION

@@ -1 +1 @@
-1.11.604
+1.11.605

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/ECSClient.h

@@ -204,14 +204,16 @@ namespace ECS
          * ECS services</a> in the <i>Amazon Elastic Container Service Developer
          * Guide</i>.</p> </li> </ul> <p>The deployment controller is the mechanism that
          * determines how tasks are deployed for your service. The valid options are:</p>
-         * <ul> <li> <p>ECS</p> <p>When you create a service which uses the
+         * <ul> <li> <p>ECS</p> <p> When you create a service which uses the
          * <code>ECS</code> deployment controller, you can choose between the following
-         * deployment strategies:</p> <ul> <li> <p> <code>ROLLING</code>: When you create a
-         * service which uses the <i>rolling update</i> (<code>ROLLING</code>) deployment
-         * strategy, the Amazon ECS service scheduler replaces the currently running tasks
-         * with new tasks. The number of tasks that Amazon ECS adds or removes from the
-         * service during a rolling update is controlled by the service deployment
-         * configuration. For more information, see <a
+         * deployment strategies (which you can set in the “<code>strategy</code>” field in
+         * “<code>deploymentConfiguration</code>”): :</p> <ul> <li> <p>
+         * <code>ROLLING</code>: When you create a service which uses the <i>rolling
+         * update</i> (<code>ROLLING</code>) deployment strategy, the Amazon ECS service
+         * scheduler replaces the currently running tasks with new tasks. The number of
+         * tasks that Amazon ECS adds or removes from the service during a rolling update
+         * is controlled by the service deployment configuration. For more information, see
+         * <a
          * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html">Deploy
          * Amazon ECS services by replacing tasks</a> in the <i>Amazon Elastic Container
          * Service Developer Guide</i>.</p> <p>Rolling update deployments are best suited

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

@@ -45,7 +45,7 @@ namespace Model
     ///@{
     /**
      * <p>The Amazon Resource Name (ARN) of the alternate target group for Amazon ECS
-     * blue/green deployments. </p>
+     * blue/green deployments.</p>
      */
     inline const Aws::String& GetAlternateTargetGroupArn() const { return m_alternateTargetGroupArn; }
     inline bool AlternateTargetGroupArnHasBeenSet() const { return m_alternateTargetGroupArnHasBeenSet; }
@@ -57,8 +57,9 @@ namespace Model
 
     ///@{
     /**
-     * <p>The Amazon Resource Name (ARN) that identifies the production listener rule
-     * for routing production traffic.</p>
+     * <p>The Amazon Resource Name (ARN) that that identifies the production listener
+     * rule (in the case of an Application Load Balancer) or listener (in the case for
+     * an Network Load Balancer) for routing production traffic.</p>
      */
     inline const Aws::String& GetProductionListenerRule() const { return m_productionListenerRule; }
     inline bool ProductionListenerRuleHasBeenSet() const { return m_productionListenerRuleHasBeenSet; }
@@ -70,8 +71,9 @@ namespace Model
 
     ///@{
     /**
-     * <p>The Amazon Resource Name (ARN) that identifies the test listener rule or
-     * listener for routing test traffic.</p>
+     * <p>The Amazon Resource Name (ARN) that identifies ) that identifies the test
+     * listener rule (in the case of an Application Load Balancer) or listener (in the
+     * case for an Network Load Balancer) for routing test traffic.</p>
      */
     inline const Aws::String& GetTestListenerRule() const { return m_testListenerRule; }
     inline bool TestListenerRuleHasBeenSet() const { return m_testListenerRuleHasBeenSet; }

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

@@ -31,8 +31,8 @@ namespace Model
    * service deployment to failed. Set the rollback parameter to have Amazon ECS to
    * roll back your service to the last completed deployment after a failure.</p>
    * <p>You can only use the <code>DeploymentAlarms</code> method to detect failures
-   * when the <code>DeploymentController</code> is set to <code>ECS</code> (rolling
-   * update).</p> <p>For more information, see <a
+   * when the <code>DeploymentController</code> is set to <code>ECS</code>.</p>
+   * <p>For more information, see <a
    * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html">Rolling
    * update</a> in the <i> <i>Amazon Elastic Container Service Developer Guide</i>
    * </i>.</p><p><h3>See Also:</h3>   <a

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

@@ -206,7 +206,7 @@ namespace Model
 
     ///@{
     /**
-     * <p>The duration when both blue and green service revisions are running
+     * <p>The time period when both blue and green service revisions are running
      * simultaneously after the production traffic has shifted.</p> <p>You must provide
      * this parameter when you use the <code>BLUE_GREEN</code> deployment strategy.</p>
      */
@@ -219,8 +219,7 @@ namespace Model
     ///@{
     /**
      * <p>An array of deployment lifecycle hook objects to run custom logic at specific
-     * stages of the deployment lifecycle. These hooks allow you to run custom logic at
-     * key points during the deployment process.</p>
+     * stages of the deployment lifecycle.</p>
      */
     inline const Aws::Vector<DeploymentLifecycleHook>& GetLifecycleHooks() const { return m_lifecycleHooks; }
     inline bool LifecycleHooksHasBeenSet() const { return m_lifecycleHooksHasBeenSet; }

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

@@ -7,7 +7,6 @@
 #include <aws/ecs/ECS_EXPORTS.h>
 #include <aws/core/utils/memory/stl/AWSString.h>
 #include <aws/core/utils/memory/stl/AWSVector.h>
-#include <aws/core/utils/Document.h>
 #include <aws/ecs/model/DeploymentLifecycleHookStage.h>
 #include <utility>
 
@@ -28,8 +27,11 @@ namespace Model
 
   /**
    * <p>A deployment lifecycle hook runs custom logic at specific stages of the
-   * deployment process. Currently, you can use Lambda functions as hook
-   * targets.</p><p><h3>See Also:</h3>   <a
+   * deployment process. Currently, you can use Lambda functions as hook targets.</p>
+   * <p>For more information, see <a
+   * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-lifecycle-hooks.html">Lifecycle
+   * hooks for Amazon ECS service deployments</a> in the <i> Amazon Elastic Container
+   * Service Developer Guide</i>.</p><p><h3>See Also:</h3>   <a
    * href="http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/DeploymentLifecycleHook">AWS
    * API Reference</a></p>
    */
@@ -62,8 +64,8 @@ namespace Model
      * permission to call Lambda functions on your behalf.</p> <p>For more information,
      * see <a
      * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/blue-green-permissions.html">Permissions
-     * required for Lambda functions in Amazon ECS blue/green deployments</a> in the<i>
-     * Amazon Elastic Container Service Developer Guide</i>.</p>
+     * required for Lambda functions in Amazon ECS blue/green deployments</a> in the
+     * <i> Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     inline const Aws::String& GetRoleArn() const { return m_roleArn; }
     inline bool RoleArnHasBeenSet() const { return m_roleArnHasBeenSet; }
@@ -76,36 +78,29 @@ namespace Model
     ///@{
     /**
      * <p>The lifecycle stages at which to run the hook. Choose from these valid
-     * values:</p> <ul> <li> <p>RECONCILE_SERVICE</p> <p>This stage only happens when
-     * you start a new service deployment with more than 1 service revision in an
-     * ACTIVE state.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li>
-     * <p>PRE_SCALE_UP</p> <p>The green service revision has not started. The blue
-     * service revision is handling 100% of the production traffic. There is no test
+     * values:</p> <ul> <li> <p>RECONCILE_SERVICE</p> <p>The reconciliation stage that
+     * only happens when you start a new service deployment with more than 1 service
+     * revision in an ACTIVE state.</p> <p>You can use a lifecycle hook for this
+     * stage.</p> </li> <li> <p>PRE_SCALE_UP</p> <p>The green service revision has not
+     * started. The blue service revision is handling 100% of the production traffic.
+     * There is no test traffic.</p> <p>You can use a lifecycle hook for this
+     * stage.</p> </li> <li> <p>POST_SCALE_UP</p> <p>The green service revision has
+     * started. The blue service revision is handling 100% of the production traffic.
+     * There is no test traffic.</p> <p>You can use a lifecycle hook for this
+     * stage.</p> </li> <li> <p>TEST_TRAFFIC_SHIFT</p> <p>The blue and green service
+     * revisions are running. The blue service revision handles 100% of the production
+     * traffic. The green service revision is migrating from 0% to 100% of test
      * traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li>
-     * <p>SCALE_UP</p> <p>The time when the green service revision scales up to 100%
-     * and launches new tasks. The green service revision is not serving any traffic at
-     * this point.</p> <p>You can't use a lifecycle hook for this stage.</p> </li> <li>
-     * <p>POST_SCALE_UP</p> <p>The green service revision has started. The blue service
-     * revision is handling 100% of the production traffic. There is no test
-     * traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li>
-     * <p>TEST_TRAFFIC_SHIFT</p> <p>The blue and green service revisions are running.
-     * The blue service revision handles 100% of the production traffic. The green
-     * service revision is migrating from 0% to 100% of test traffic.</p> <p>You can
-     * use a lifecycle hook for this stage.</p> </li> <li>
      * <p>POST_TEST_TRAFFIC_SHIFT</p> <p>The test traffic shift is complete. The green
      * service revision handles 100% of the test traffic.</p> <p>You can use a
      * lifecycle hook for this stage.</p> </li> <li> <p>PRODUCTION_TRAFFIC_SHIFT</p>
      * <p>Production traffic is shifting to the green service revision. The green
      * service revision is migrating from 0% to 100% of production traffic.</p> <p>You
      * can use a lifecycle hook for this stage.</p> </li> <li>
      * <p>POST_PRODUCTION_TRAFFIC_SHIFT</p> <p>The production traffic shift is
-     * complete.</p> <p>Yes</p> </li> <li> <p>BAKE_TIME</p> <p>The duration when both
-     * blue and green service revisions are running simultaneously.</p> <p>You can't
-     * use a lifecycle hook for this stage.</p> </li> <li> <p>CLEAN_UP</p> <p>The blue
-     * service revision has completely scaled down to 0 running tasks. The green
-     * service revision is now the production service revision after this stage.</p>
-     * <p>You can't use a lifecycle hook for this stage.</p> </li> </ul> <p>You must
-     * provide this parameter when configuring a deployment lifecycle hook.</p>
+     * complete.</p> <p>You can use a lifecycle hook for this stage.</p> </li> </ul>
+     * <p>You must provide this parameter when configuring a deployment lifecycle
+     * hook.</p>
      */
     inline const Aws::Vector<DeploymentLifecycleHookStage>& GetLifecycleStages() const { return m_lifecycleStages; }
     inline bool LifecycleStagesHasBeenSet() const { return m_lifecycleStagesHasBeenSet; }
@@ -115,19 +110,6 @@ namespace Model
     DeploymentLifecycleHook& WithLifecycleStages(LifecycleStagesT&& value) { SetLifecycleStages(std::forward<LifecycleStagesT>(value)); return *this;}
     inline DeploymentLifecycleHook& AddLifecycleStages(DeploymentLifecycleHookStage value) { m_lifecycleStagesHasBeenSet = true; m_lifecycleStages.push_back(value); return *this; }
     ///@}
-
-    ///@{
-    /**
-     * <p>Optionally provide details about the hook. Use this field to pass custom
-     * parameters to your hook target (such as a Lambda function).</p>
-     */
-    inline Aws::Utils::DocumentView GetHookDetails() const { return m_hookDetails; }
-    inline bool HookDetailsHasBeenSet() const { return m_hookDetailsHasBeenSet; }
-    template<typename HookDetailsT = Aws::Utils::Document>
-    void SetHookDetails(HookDetailsT&& value) { m_hookDetailsHasBeenSet = true; m_hookDetails = std::forward<HookDetailsT>(value); }
-    template<typename HookDetailsT = Aws::Utils::Document>
-    DeploymentLifecycleHook& WithHookDetails(HookDetailsT&& value) { SetHookDetails(std::forward<HookDetailsT>(value)); return *this;}
-    ///@}
   private:
 
     Aws::String m_hookTargetArn;
@@ -138,9 +120,6 @@ namespace Model
 
     Aws::Vector<DeploymentLifecycleHookStage> m_lifecycleStages;
     bool m_lifecycleStagesHasBeenSet = false;
-
-    Aws::Utils::Document m_hookDetails;
-    bool m_hookDetailsHasBeenSet = false;
   };
 
 } // namespace Model

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

@@ -27,7 +27,11 @@ namespace Model
   /**
    * <p>The HTTP header rules used to identify and route test traffic during Amazon
    * ECS blue/green deployments. These rules specify which HTTP headers to examine
-   * and what values to match for routing decisions.</p><p><h3>See Also:</h3>   <a
+   * and what values to match for routing decisions.</p> <p>For more information, see
+   * <a
+   * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect-blue-green.html">Service
+   * Connect for Amazon ECS blue/green deployments</a> in the <i> Amazon Elastic
+   * Container Service Developer Guide</i>.</p><p><h3>See Also:</h3>   <a
    * href="http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ServiceConnectTestTrafficHeaderRules">AWS
    * API Reference</a></p>
    */

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

@@ -27,7 +27,11 @@ namespace Model
    * <p>The test traffic routing configuration for Amazon ECS blue/green deployments.
    * This configuration allows you to define rules for routing specific traffic to
    * the new service revision during the deployment process, allowing for safe
-   * testing before full production traffic shift.</p><p><h3>See Also:</h3>   <a
+   * testing before full production traffic shift.</p> <p>For more information, see
+   * <a
+   * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect-blue-green.html">Service
+   * Connect for Amazon ECS blue/green deployments</a> in the <i> Amazon Elastic
+   * Container Service Developer Guide</i>.</p><p><h3>See Also:</h3>   <a
    * href="http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ServiceConnectTestTrafficRules">AWS
    * API Reference</a></p>
    */

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

@@ -208,15 +208,29 @@ namespace Model
     ///@{
     /**
      * <p>The current lifecycle stage of the deployment. Possible values include:</p>
-     * <ul> <li> <p> <code>SCALE_UP_IN_PROGRESS</code> - Creating the new (green)
-     * tasks</p> </li> <li> <p> <code>TEST_TRAFFIC_SHIFT_IN_PROGRESS</code> - Shifting
-     * test traffic to the new (green) tasks</p> </li> <li> <p>
-     * <code>PRODUCTION_TRAFFIC_SHIFT_IN_PROGRESS</code> - Shifting production traffic
-     * to the new (green) tasks</p> </li> <li> <p> <code>BAKE_TIME_IN_PROGRESS</code> -
-     * The duration when both blue and green service revisions are running
-     * simultaneously after the production traffic has shifted</p> </li> <li> <p>
-     * <code>CLEAN_UP_IN_PROGRESS</code> - Stopping the old (blue) tasks</p> </li>
-     * </ul>
+     * <ul> <li> <p>RECONCILE_SERVICE</p> <p>The reconciliation stage that only happens
+     * when you start a new service deployment with more than 1 service revision in an
+     * ACTIVE state.</p> </li> <li> <p>PRE_SCALE_UP</p> <p>The green service revision
+     * has not started. The blue service revision is handling 100% of the production
+     * traffic. There is no test traffic.</p> </li> <li> <p>SCALE_UP</p> <p>The stage
+     * when the green service revision scales up to 100% and launches new tasks. The
+     * green service revision is not serving any traffic at this point.</p> </li> <li>
+     * <p>POST_SCALE_UP</p> <p>The green service revision has started. The blue service
+     * revision is handling 100% of the production traffic. There is no test
+     * traffic.</p> </li> <li> <p>TEST_TRAFFIC_SHIFT</p> <p>The blue and green service
+     * revisions are running. The blue service revision handles 100% of the production
+     * traffic. The green service revision is migrating from 0% to 100% of test
+     * traffic.</p> </li> <li> <p>POST_TEST_TRAFFIC_SHIFT</p> <p>The test traffic shift
+     * is complete. The green service revision handles 100% of the test traffic.</p>
+     * </li> <li> <p>PRODUCTION_TRAFFIC_SHIFT</p> <p>Production traffic is shifting to
+     * the green service revision. The green service revision is migrating from 0% to
+     * 100% of production traffic.</p> </li> <li> <p>POST_PRODUCTION_TRAFFIC_SHIFT</p>
+     * <p>The production traffic shift is complete.</p> </li> <li> <p>BAKE_TIME</p>
+     * <p>The stage when both blue and green service revisions are running
+     * simultaneously after the production traffic has shifted.</p> </li> <li>
+     * <p>CLEAN_UP</p> <p>The stage when the blue service revision has completely
+     * scaled down to 0 running tasks. The green service revision is now the production
+     * service revision after this stage.</p> </li> </ul>
      */
     inline ServiceDeploymentLifecycleStage GetLifecycleStage() const { return m_lifecycleStage; }
     inline bool LifecycleStageHasBeenSet() const { return m_lifecycleStageHasBeenSet; }

generated/src/aws-cpp-sdk-ecs/source/model/DeploymentLifecycleHook.cpp

@@ -44,11 +44,6 @@ DeploymentLifecycleHook& DeploymentLifecycleHook::operator =(JsonView jsonValue)
     }
     m_lifecycleStagesHasBeenSet = true;
   }
-  if(jsonValue.ValueExists("hookDetails"))
-  {
-    m_hookDetails = jsonValue.GetObject("hookDetails");
-    m_hookDetailsHasBeenSet = true;
-  }
   return *this;
 }
 
@@ -79,14 +74,6 @@ JsonValue DeploymentLifecycleHook::Jsonize() const
 
   }
 
-  if(m_hookDetailsHasBeenSet)
-  {
-    if(!m_hookDetails.View().IsNull())
-    {
-       payload.WithObject("hookDetails", JsonValue(m_hookDetails.View()));
-    }
-  }
-
   return payload;
 }