AWS cli documentation change
Summary
Updated CLI version reference from 2.27.50 to 2.27.51
Security assessment
Routine version number update without any security context or changes to functionality documentation
Diff
diff --git a/cli/latest/reference/ecs/describe-service-deployments.md b/cli/latest/reference/ecs/describe-service-deployments.md index a3838c7a7..724c94485 100644 --- a//cli/latest/reference/ecs/describe-service-deployments.md +++ b//cli/latest/reference/ecs/describe-service-deployments.md @@ -15 +15 @@ - * [AWS CLI 2.27.50 Command Reference](../../index.html) » + * [AWS CLI 2.27.51 Command Reference](../../index.html) » @@ -65,0 +66,2 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/ecs-20 +`describe-service-deployments` uses document type values. Document types follow the JSON data model where valid values are: strings, numbers, booleans, null, arrays, and objects. For command input, options and nested parameters that are labeled with the type `document` must be provided as JSON. Shorthand syntax does not support document types. + @@ -374,0 +377,12 @@ serviceDeployments -> (list) +>> +>> lifecycleStage -> (string) +>> +>>> The current lifecycle stage of the deployment. Possible values include: +>>> +>>> * `SCALE_UP_IN_PROGRESS` \- Creating the new (green) tasks +>>> * `TEST_TRAFFIC_SHIFT_IN_PROGRESS` \- Shifting test traffic to the new (green) tasks +>>> * `PRODUCTION_TRAFFIC_SHIFT_IN_PROGRESS` \- Shifting production traffic to the new (green) tasks +>>> * `BAKE_TIME_IN_PROGRESS` \- The duration when both blue and green service revisions are running simultaneously after the production traffic has shifted +>>> * `CLEAN_UP_IN_PROGRESS` \- Stopping the old (blue) tasks +>>> + @@ -459,0 +474,60 @@ serviceDeployments -> (list) +>>> +>>> strategy -> (string) +>>> +>>>> The deployment strategy for the service. Choose from these valid values: +>>>> +>>>> * `ROLLING` \- When you create a service which uses the rolling update (`ROLLING` ) 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. +>>>> * `BLUE_GREEN` \- A blue/green deployment strategy (`BLUE_GREEN` ) is a release methodology that reduces downtime and risk by running two identical production environments called blue and green. With Amazon ECS blue/green deployments, you can validate new service revisions before directing production traffic to them. This approach provides a safer way to deploy changes with the ability to quickly roll back if needed. +>>>> + +>>> +>>> bakeTimeInMinutes -> (integer) +>>> +>>>> The duration when both blue and green service revisions are running simultaneously after the production traffic has shifted. +>>>> +>>>> You must provide this parameter when you use the `BLUE_GREEN` deployment strategy. +>>> +>>> lifecycleHooks -> (list) +>>> +>>>> 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. +>>>> +>>>> (structure) +>>>> +>>>>> A deployment lifecycle hook runs custom logic at specific stages of the deployment process. Currently, you can use Lambda functions as hook targets. +>>>>> +>>>>> hookTargetArn -> (string) +>>>>> +>>>>>> The Amazon Resource Name (ARN) of the hook target. Currently, only Lambda function ARNs are supported. +>>>>>> +>>>>>> You must provide this parameter when configuring a deployment lifecycle hook. +>>>>> +>>>>> roleArn -> (string) +>>>>> +>>>>>> The Amazon Resource Name (ARN) of the IAM role that grants Amazon ECS permission to call Lambda functions on your behalf. +>>>>>> +>>>>>> For more information, see [Permissions required for Lambda functions in Amazon ECS blue/green deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/blue-green-permissions.html) in the*Amazon Elastic Container Service Developer Guide* . +>>>>> +>>>>> lifecycleStages -> (list) +>>>>> +>>>>>> The lifecycle stages at which to run the hook. Choose from these valid values: +>>>>>> +>>>>>> * RECONCILE_SERVICE This stage only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state. You can use a lifecycle hook for this stage. +>>>>>> * PRE_SCALE_UP The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic. You can use a lifecycle hook for this stage. +>>>>>> * SCALE_UP 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. You can’t use a lifecycle hook for this stage. +>>>>>> * POST_SCALE_UP The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic. You can use a lifecycle hook for this stage. +>>>>>> * TEST_TRAFFIC_SHIFT 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. You can use a lifecycle hook for this stage. +>>>>>> * POST_TEST_TRAFFIC_SHIFT The test traffic shift is complete. The green service revision handles 100% of the test traffic. You can use a lifecycle hook for this stage. +>>>>>> * PRODUCTION_TRAFFIC_SHIFT Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic. You can use a lifecycle hook for this stage. +>>>>>> * POST_PRODUCTION_TRAFFIC_SHIFT The production traffic shift is complete. Yes +>>>>>> * BAKE_TIME The duration when both blue and green service revisions are running simultaneously. You can’t use a lifecycle hook for this stage. +>>>>>> * CLEAN_UP 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. You can’t use a lifecycle hook for this stage. +>>>>>> + +>>>>>> +>>>>>> You must provide this parameter when configuring a deployment lifecycle hook. +>>>>>> +>>>>>> (string) +>>>>> +>>>>> hookDetails -> (document) +>>>>> +>>>>>> Optionally provide details about the hook. Use this field to pass custom parameters to your hook target (such as a Lambda function). @@ -549 +623 @@ failures -> (list) - * [AWS CLI 2.27.50 Command Reference](../../index.html) » + * [AWS CLI 2.27.51 Command Reference](../../index.html) »