AWS SDK for C++  1.8.95
AWS SDK for C++
Public Member Functions | List of all members
Aws::ECS::Model::DeploymentConfiguration Class Reference

#include <DeploymentConfiguration.h>

Public Member Functions

 DeploymentConfiguration ()
 
 DeploymentConfiguration (Aws::Utils::Json::JsonView jsonValue)
 
DeploymentConfigurationoperator= (Aws::Utils::Json::JsonView jsonValue)
 
Aws::Utils::Json::JsonValue Jsonize () const
 
const DeploymentCircuitBreakerGetDeploymentCircuitBreaker () const
 
bool DeploymentCircuitBreakerHasBeenSet () const
 
void SetDeploymentCircuitBreaker (const DeploymentCircuitBreaker &value)
 
void SetDeploymentCircuitBreaker (DeploymentCircuitBreaker &&value)
 
DeploymentConfigurationWithDeploymentCircuitBreaker (const DeploymentCircuitBreaker &value)
 
DeploymentConfigurationWithDeploymentCircuitBreaker (DeploymentCircuitBreaker &&value)
 
int GetMaximumPercent () const
 
bool MaximumPercentHasBeenSet () const
 
void SetMaximumPercent (int value)
 
DeploymentConfigurationWithMaximumPercent (int value)
 
int GetMinimumHealthyPercent () const
 
bool MinimumHealthyPercentHasBeenSet () const
 
void SetMinimumHealthyPercent (int value)
 
DeploymentConfigurationWithMinimumHealthyPercent (int value)
 

Detailed Description

Optional deployment parameters that control how many tasks run during a deployment and the ordering of stopping and starting tasks.

See Also:

AWS API Reference

Definition at line 33 of file DeploymentConfiguration.h.

Constructor & Destructor Documentation

◆ DeploymentConfiguration() [1/2]

Aws::ECS::Model::DeploymentConfiguration::DeploymentConfiguration ( )

◆ DeploymentConfiguration() [2/2]

Aws::ECS::Model::DeploymentConfiguration::DeploymentConfiguration ( Aws::Utils::Json::JsonView  jsonValue)

Member Function Documentation

◆ DeploymentCircuitBreakerHasBeenSet()

bool Aws::ECS::Model::DeploymentConfiguration::DeploymentCircuitBreakerHasBeenSet ( ) const
inline

The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type.

The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

Definition at line 64 of file DeploymentConfiguration.h.

◆ GetDeploymentCircuitBreaker()

const DeploymentCircuitBreaker& Aws::ECS::Model::DeploymentConfiguration::GetDeploymentCircuitBreaker ( ) const
inline

The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type.

The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

Definition at line 52 of file DeploymentConfiguration.h.

◆ GetMaximumPercent()

int Aws::ECS::Model::DeploymentConfiguration::GetMaximumPercent ( ) const
inline

If a service is using the rolling update (ECS) deployment type, the maximum percent parameter represents an upper limit on the number of tasks in a service that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desired number of tasks (rounded down to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to define the deployment batch size. For example, if your service has a desired number of four tasks and a maximum percent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default value for maximum percent is 200%.

If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.

Definition at line 136 of file DeploymentConfiguration.h.

◆ GetMinimumHealthyPercent()

int Aws::ECS::Model::DeploymentConfiguration::GetMinimumHealthyPercent ( ) const
inline

If a service is using the rolling update (ECS) deployment type, the minimum healthy percent represents a lower limit on the number of tasks in a service that must remain in the RUNNING state during a deployment, as a percentage of the desired number of tasks (rounded up to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desired number of four tasks and a minimum healthy percent of 50%, the scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state; tasks for services that do use a load balancer are considered healthy if they are in the RUNNING state and they are reported as healthy by the load balancer. The default value for minimum healthy percent is 100%.

If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

Definition at line 232 of file DeploymentConfiguration.h.

◆ Jsonize()

Aws::Utils::Json::JsonValue Aws::ECS::Model::DeploymentConfiguration::Jsonize ( ) const

◆ MaximumPercentHasBeenSet()

bool Aws::ECS::Model::DeploymentConfiguration::MaximumPercentHasBeenSet ( ) const
inline

If a service is using the rolling update (ECS) deployment type, the maximum percent parameter represents an upper limit on the number of tasks in a service that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desired number of tasks (rounded down to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to define the deployment batch size. For example, if your service has a desired number of four tasks and a maximum percent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default value for maximum percent is 200%.

If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.

Definition at line 159 of file DeploymentConfiguration.h.

◆ MinimumHealthyPercentHasBeenSet()

bool Aws::ECS::Model::DeploymentConfiguration::MinimumHealthyPercentHasBeenSet ( ) const
inline

If a service is using the rolling update (ECS) deployment type, the minimum healthy percent represents a lower limit on the number of tasks in a service that must remain in the RUNNING state during a deployment, as a percentage of the desired number of tasks (rounded up to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desired number of four tasks and a minimum healthy percent of 50%, the scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state; tasks for services that do use a load balancer are considered healthy if they are in the RUNNING state and they are reported as healthy by the load balancer. The default value for minimum healthy percent is 100%.

If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

Definition at line 258 of file DeploymentConfiguration.h.

◆ operator=()

DeploymentConfiguration& Aws::ECS::Model::DeploymentConfiguration::operator= ( Aws::Utils::Json::JsonView  jsonValue)

◆ SetDeploymentCircuitBreaker() [1/2]

void Aws::ECS::Model::DeploymentConfiguration::SetDeploymentCircuitBreaker ( const DeploymentCircuitBreaker value)
inline

The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type.

The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

Definition at line 76 of file DeploymentConfiguration.h.

◆ SetDeploymentCircuitBreaker() [2/2]

void Aws::ECS::Model::DeploymentConfiguration::SetDeploymentCircuitBreaker ( DeploymentCircuitBreaker &&  value)
inline

The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type.

The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

Definition at line 88 of file DeploymentConfiguration.h.

◆ SetMaximumPercent()

void Aws::ECS::Model::DeploymentConfiguration::SetMaximumPercent ( int  value)
inline

If a service is using the rolling update (ECS) deployment type, the maximum percent parameter represents an upper limit on the number of tasks in a service that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desired number of tasks (rounded down to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to define the deployment batch size. For example, if your service has a desired number of four tasks and a maximum percent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default value for maximum percent is 200%.

If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.

Definition at line 182 of file DeploymentConfiguration.h.

◆ SetMinimumHealthyPercent()

void Aws::ECS::Model::DeploymentConfiguration::SetMinimumHealthyPercent ( int  value)
inline

If a service is using the rolling update (ECS) deployment type, the minimum healthy percent represents a lower limit on the number of tasks in a service that must remain in the RUNNING state during a deployment, as a percentage of the desired number of tasks (rounded up to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desired number of four tasks and a minimum healthy percent of 50%, the scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state; tasks for services that do use a load balancer are considered healthy if they are in the RUNNING state and they are reported as healthy by the load balancer. The default value for minimum healthy percent is 100%.

If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

Definition at line 284 of file DeploymentConfiguration.h.

◆ WithDeploymentCircuitBreaker() [1/2]

DeploymentConfiguration& Aws::ECS::Model::DeploymentConfiguration::WithDeploymentCircuitBreaker ( const DeploymentCircuitBreaker value)
inline

The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type.

The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

Definition at line 100 of file DeploymentConfiguration.h.

◆ WithDeploymentCircuitBreaker() [2/2]

DeploymentConfiguration& Aws::ECS::Model::DeploymentConfiguration::WithDeploymentCircuitBreaker ( DeploymentCircuitBreaker &&  value)
inline

The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type.

The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

Definition at line 112 of file DeploymentConfiguration.h.

◆ WithMaximumPercent()

DeploymentConfiguration& Aws::ECS::Model::DeploymentConfiguration::WithMaximumPercent ( int  value)
inline

If a service is using the rolling update (ECS) deployment type, the maximum percent parameter represents an upper limit on the number of tasks in a service that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desired number of tasks (rounded down to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to define the deployment batch size. For example, if your service has a desired number of four tasks and a maximum percent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default value for maximum percent is 200%.

If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.

Definition at line 205 of file DeploymentConfiguration.h.

◆ WithMinimumHealthyPercent()

DeploymentConfiguration& Aws::ECS::Model::DeploymentConfiguration::WithMinimumHealthyPercent ( int  value)
inline

If a service is using the rolling update (ECS) deployment type, the minimum healthy percent represents a lower limit on the number of tasks in a service that must remain in the RUNNING state during a deployment, as a percentage of the desired number of tasks (rounded up to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desired number of four tasks and a minimum healthy percent of 50%, the scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state; tasks for services that do use a load balancer are considered healthy if they are in the RUNNING state and they are reported as healthy by the load balancer. The default value for minimum healthy percent is 100%.

If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

Definition at line 310 of file DeploymentConfiguration.h.


The documentation for this class was generated from the following file: