com.amazonaws.services.ecs.model.DeploymentConfiguration Maven / Gradle / Ivy
Show all versions of aws-java-sdk-ecs Show documentation
/*
* Copyright 2015-2020 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with
* the License. A copy of the License is located at
*
* http://aws.amazon.com/apache2.0
*
* or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
* CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions
* and limitations under the License.
*/
package com.amazonaws.services.ecs.model;
import java.io.Serializable;
import javax.annotation.Generated;
import com.amazonaws.protocol.StructuredPojo;
import com.amazonaws.protocol.ProtocolMarshaller;
/**
*
* Optional deployment parameters that control how many tasks run during a deployment and the ordering of stopping and
* starting tasks.
*
*
* @see AWS API
* Documentation
*/
@Generated("com.amazonaws:aws-java-sdk-code-generator")
public class DeploymentConfiguration implements Serializable, Cloneable, StructuredPojo {
/**
*
* 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.
*
*/
private Integer maximumPercent;
/**
*
* 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.
*
*/
private Integer minimumHealthyPercent;
/**
*
* 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.
*
*
* @param maximumPercent
* 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.
*/
public void setMaximumPercent(Integer maximumPercent) {
this.maximumPercent = maximumPercent;
}
/**
*
* 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.
*
*
* @return 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.
*/
public Integer getMaximumPercent() {
return this.maximumPercent;
}
/**
*
* 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.
*
*
* @param maximumPercent
* 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.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public DeploymentConfiguration withMaximumPercent(Integer maximumPercent) {
setMaximumPercent(maximumPercent);
return this;
}
/**
*
* 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.
*
*
* @param minimumHealthyPercent
* 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.
*/
public void setMinimumHealthyPercent(Integer minimumHealthyPercent) {
this.minimumHealthyPercent = minimumHealthyPercent;
}
/**
*
* 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.
*
*
* @return 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.
*/
public Integer getMinimumHealthyPercent() {
return this.minimumHealthyPercent;
}
/**
*
* 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.
*
*
* @param minimumHealthyPercent
* 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.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public DeploymentConfiguration withMinimumHealthyPercent(Integer minimumHealthyPercent) {
setMinimumHealthyPercent(minimumHealthyPercent);
return this;
}
/**
* Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be
* redacted from this string using a placeholder value.
*
* @return A string representation of this object.
*
* @see java.lang.Object#toString()
*/
@Override
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
if (getMaximumPercent() != null)
sb.append("MaximumPercent: ").append(getMaximumPercent()).append(",");
if (getMinimumHealthyPercent() != null)
sb.append("MinimumHealthyPercent: ").append(getMinimumHealthyPercent());
sb.append("}");
return sb.toString();
}
@Override
public boolean equals(Object obj) {
if (this == obj)
return true;
if (obj == null)
return false;
if (obj instanceof DeploymentConfiguration == false)
return false;
DeploymentConfiguration other = (DeploymentConfiguration) obj;
if (other.getMaximumPercent() == null ^ this.getMaximumPercent() == null)
return false;
if (other.getMaximumPercent() != null && other.getMaximumPercent().equals(this.getMaximumPercent()) == false)
return false;
if (other.getMinimumHealthyPercent() == null ^ this.getMinimumHealthyPercent() == null)
return false;
if (other.getMinimumHealthyPercent() != null && other.getMinimumHealthyPercent().equals(this.getMinimumHealthyPercent()) == false)
return false;
return true;
}
@Override
public int hashCode() {
final int prime = 31;
int hashCode = 1;
hashCode = prime * hashCode + ((getMaximumPercent() == null) ? 0 : getMaximumPercent().hashCode());
hashCode = prime * hashCode + ((getMinimumHealthyPercent() == null) ? 0 : getMinimumHealthyPercent().hashCode());
return hashCode;
}
@Override
public DeploymentConfiguration clone() {
try {
return (DeploymentConfiguration) super.clone();
} catch (CloneNotSupportedException e) {
throw new IllegalStateException("Got a CloneNotSupportedException from Object.clone() " + "even though we're Cloneable!", e);
}
}
@com.amazonaws.annotation.SdkInternalApi
@Override
public void marshall(ProtocolMarshaller protocolMarshaller) {
com.amazonaws.services.ecs.model.transform.DeploymentConfigurationMarshaller.getInstance().marshall(this, protocolMarshaller);
}
}