You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: clients/client-ecs/src/models/models_0.ts
+47-43Lines changed: 47 additions & 43 deletions
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
1
// smithy-typescript generated code
2
2
import { ExceptionOptionType as __ExceptionOptionType, SENSITIVE_STRING } from "@smithy/smithy-client";
3
3
4
-
import { DocumentType as __DocumentType } from "@smithy/types";
5
-
6
4
import { ECSServiceException as __BaseException } from "./ECSServiceException";
7
5
8
6
/**
@@ -34,19 +32,21 @@ export class AccessDeniedException extends __BaseException {
34
32
*/
35
33
export interface AdvancedConfiguration {
36
34
/**
37
-
* <p>The Amazon Resource Name (ARN) of the alternate target group for Amazon ECS blue/green deployments.</p>
35
+
* <p>The Amazon Resource Name (ARN) of the alternate target group for Amazon ECS blue/green deployments.</p>
38
36
* @public
39
37
*/
40
38
alternateTargetGroupArn?: string | undefined;
41
39
42
40
/**
43
-
* <p>The Amazon Resource Name (ARN) that identifies the production listener rule for routing production traffic.</p>
41
+
* <p>The Amazon Resource Name (ARN) that that identifies the production listener rule (in the case of an Application Load Balancer) or
42
+
* listener (in the case for an Network Load Balancer) for routing production traffic.</p>
44
43
* @public
45
44
*/
46
45
productionListenerRule?: string | undefined;
47
46
48
47
/**
49
-
* <p>The Amazon Resource Name (ARN) that identifies the test listener rule or listener for routing test traffic.</p>
48
+
* <p>The Amazon Resource Name (ARN) that identifies ) that identifies the test listener rule (in the case of an Application Load Balancer) or
49
+
* listener (in the case for an Network Load Balancer) for routing test traffic.</p>
50
50
* @public
51
51
*/
52
52
testListenerRule?: string | undefined;
@@ -1393,8 +1393,7 @@ export type AvailabilityZoneRebalancing =
1393
1393
* rollback parameter to have Amazon ECS to roll back your service to the last completed
1394
1394
* deployment after a failure.</p>
1395
1395
* <p>You can only use the <code>DeploymentAlarms</code> method to detect failures when the
1396
-
* <code>DeploymentController</code> is set to <code>ECS</code> (rolling
1397
-
* update).</p>
1396
+
* <code>DeploymentController</code> is set to <code>ECS</code>.</p>
1398
1397
* <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html">Rolling
1399
1398
* update</a> in the <i>
1400
1399
* <i>Amazon Elastic Container Service Developer Guide</i>
@@ -1477,6 +1476,8 @@ export type DeploymentLifecycleHookStage =
1477
1476
1478
1477
/**
1479
1478
* <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>
1479
+
* <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>
1480
+
* Amazon Elastic Container Service Developer Guide</i>.</p>
* <p>You can use a lifecycle hook for this stage.</p>
1511
1512
* </li>
1512
1513
* <li>
1513
-
* <p>SCALE_UP</p>
1514
-
* <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>
1515
-
* <p>You can't use a lifecycle hook for this stage.</p>
1516
-
* </li>
1517
-
* <li>
1518
1514
* <p>POST_SCALE_UP</p>
1519
1515
* <p>The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p>
1520
1516
* <p>You can use a lifecycle hook for this stage.</p>
* <p>The production traffic shift is complete.</p>
1540
-
* <p>Yes</p>
1541
-
* </li>
1542
-
* <li>
1543
-
* <p>BAKE_TIME</p>
1544
-
* <p>The duration when both blue and green service revisions are running simultaneously.</p>
1545
-
* <p>You can't use a lifecycle hook for this stage.</p>
1546
-
* </li>
1547
-
* <li>
1548
-
* <p>CLEAN_UP</p>
1549
-
* <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>
1550
-
* <p>You can't use a lifecycle hook for this stage.</p>
1536
+
* <p>You can use a lifecycle hook for this stage.</p>
1551
1537
* </li>
1552
1538
* </ul>
1553
1539
* <p>You must provide this parameter when configuring a deployment lifecycle hook.</p>
* <p>The duration when both blue and green service revisions are running simultaneously after the production traffic has shifted.</p>
1730
+
* <p>The time period when both blue and green service revisions are running simultaneously after the production traffic has shifted.</p>
1751
1731
* <p>You must provide this parameter when you use the <code>BLUE_GREEN</code> deployment
1752
1732
* strategy.</p>
1753
1733
* @public
1754
1734
*/
1755
1735
bakeTimeInMinutes?: number | undefined;
1756
1736
1757
1737
/**
1758
-
* <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>
1738
+
* <p>An array of deployment lifecycle hook objects to run custom logic at specific stages of the deployment lifecycle.</p>
* <p>The HTTP header rules used to identify and route test traffic during Amazon ECS blue/green
2497
2477
* deployments. These rules specify which HTTP headers to examine and what values to match for
2498
2478
* routing decisions.</p>
2479
+
* <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>
2480
+
* Amazon Elastic Container Service Developer Guide</i>.</p>
* configuration allows you to define rules for routing specific traffic to the new service
2518
2500
* revision during the deployment process, allowing for safe testing before full production
2519
2501
* traffic shift.</p>
2502
+
* <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>
2503
+
* Amazon Elastic Container Service Developer Guide</i>.</p>
* <p>The current lifecycle stage of the deployment. Possible values include:</p>
9023
9007
* <ul>
9024
9008
* <li>
9025
-
* <p>
9026
-
* <code>SCALE_UP_IN_PROGRESS</code> - Creating the new (green) tasks</p>
9009
+
* <p>RECONCILE_SERVICE</p>
9010
+
* <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>
9027
9011
* </li>
9028
9012
* <li>
9029
-
* <p>
9030
-
* <code>TEST_TRAFFIC_SHIFT_IN_PROGRESS</code> - Shifting test traffic to the new (green) tasks</p>
9013
+
* <p>PRE_SCALE_UP</p>
9014
+
* <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>
9031
9015
* </li>
9032
9016
* <li>
9033
-
* <p>
9034
-
* <code>PRODUCTION_TRAFFIC_SHIFT_IN_PROGRESS</code> - Shifting production traffic to the new (green) tasks</p>
9017
+
* <p>SCALE_UP</p>
9018
+
* <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>
9035
9019
* </li>
9036
9020
* <li>
9037
-
* <p>
9038
-
* <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>
9021
+
* <p>POST_SCALE_UP</p>
9022
+
* <p>The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p>
9039
9023
* </li>
9040
9024
* <li>
9041
-
* <p>
9042
-
* <code>CLEAN_UP_IN_PROGRESS</code> - Stopping the old (blue) tasks</p>
9025
+
* <p>TEST_TRAFFIC_SHIFT</p>
9026
+
* <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>
9027
+
* </li>
9028
+
* <li>
9029
+
* <p>POST_TEST_TRAFFIC_SHIFT</p>
9030
+
* <p>The test traffic shift is complete. The green service revision handles 100% of the test traffic.</p>
9031
+
* </li>
9032
+
* <li>
9033
+
* <p>PRODUCTION_TRAFFIC_SHIFT</p>
9034
+
* <p>Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic.</p>
9035
+
* </li>
9036
+
* <li>
9037
+
* <p>POST_PRODUCTION_TRAFFIC_SHIFT</p>
9038
+
* <p>The production traffic shift is complete.</p>
9039
+
* </li>
9040
+
* <li>
9041
+
* <p>BAKE_TIME</p>
9042
+
* <p>The stage when both blue and green service revisions are running simultaneously after the production traffic has shifted.</p>
9043
+
* </li>
9044
+
* <li>
9045
+
* <p>CLEAN_UP</p>
9046
+
* <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>
0 commit comments