@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class CreateDeploymentRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
 Represents the input of a CreateDeployment operation.
 
NOOP| Constructor and Description | 
|---|
| CreateDeploymentRequest() | 
| Modifier and Type | Method and Description | 
|---|---|
| CreateDeploymentRequest | clone()Creates a shallow clone of this object for all fields except the handler context. | 
| boolean | equals(Object obj) | 
| String | getApplicationName()
 The name of an CodeDeploy application associated with the user or Amazon Web Services account. | 
| AutoRollbackConfiguration | getAutoRollbackConfiguration()
 Configuration information for an automatic rollback that is added when a deployment is created. | 
| String | getDeploymentConfigName()
 The name of a deployment configuration associated with the user or Amazon Web Services account. | 
| String | getDeploymentGroupName()
 The name of the deployment group. | 
| String | getDescription()
 A comment about the deployment. | 
| String | getFileExistsBehavior()
 Information about how CodeDeploy handles files that already exist in a deployment target location but weren't
 part of the previous successful deployment. | 
| Boolean | getIgnoreApplicationStopFailures()
 If true, then if an  ApplicationStop,BeforeBlockTraffic, orAfterBlockTrafficdeployment lifecycle event to an instance fails, then the deployment continues to
 the next deployment lifecycle event. | 
| AlarmConfiguration | getOverrideAlarmConfiguration()
 Allows you to specify information about alarms associated with a deployment. | 
| RevisionLocation | getRevision()
 The type and location of the revision to deploy. | 
| TargetInstances | getTargetInstances()
 Information about the instances that belong to the replacement environment in a blue/green deployment. | 
| Boolean | getUpdateOutdatedInstancesOnly()
 Indicates whether to deploy to all instances or only to instances that are not running the latest application
 revision. | 
| int | hashCode() | 
| Boolean | isIgnoreApplicationStopFailures()
 If true, then if an  ApplicationStop,BeforeBlockTraffic, orAfterBlockTrafficdeployment lifecycle event to an instance fails, then the deployment continues to
 the next deployment lifecycle event. | 
| Boolean | isUpdateOutdatedInstancesOnly()
 Indicates whether to deploy to all instances or only to instances that are not running the latest application
 revision. | 
| void | setApplicationName(String applicationName)
 The name of an CodeDeploy application associated with the user or Amazon Web Services account. | 
| void | setAutoRollbackConfiguration(AutoRollbackConfiguration autoRollbackConfiguration)
 Configuration information for an automatic rollback that is added when a deployment is created. | 
| void | setDeploymentConfigName(String deploymentConfigName)
 The name of a deployment configuration associated with the user or Amazon Web Services account. | 
| void | setDeploymentGroupName(String deploymentGroupName)
 The name of the deployment group. | 
| void | setDescription(String description)
 A comment about the deployment. | 
| void | setFileExistsBehavior(FileExistsBehavior fileExistsBehavior)
 Information about how CodeDeploy handles files that already exist in a deployment target location but weren't
 part of the previous successful deployment. | 
| void | setFileExistsBehavior(String fileExistsBehavior)
 Information about how CodeDeploy handles files that already exist in a deployment target location but weren't
 part of the previous successful deployment. | 
| void | setIgnoreApplicationStopFailures(Boolean ignoreApplicationStopFailures)
 If true, then if an  ApplicationStop,BeforeBlockTraffic, orAfterBlockTrafficdeployment lifecycle event to an instance fails, then the deployment continues to
 the next deployment lifecycle event. | 
| void | setOverrideAlarmConfiguration(AlarmConfiguration overrideAlarmConfiguration)
 Allows you to specify information about alarms associated with a deployment. | 
| void | setRevision(RevisionLocation revision)
 The type and location of the revision to deploy. | 
| void | setTargetInstances(TargetInstances targetInstances)
 Information about the instances that belong to the replacement environment in a blue/green deployment. | 
| void | setUpdateOutdatedInstancesOnly(Boolean updateOutdatedInstancesOnly)
 Indicates whether to deploy to all instances or only to instances that are not running the latest application
 revision. | 
| String | toString()Returns a string representation of this object. | 
| CreateDeploymentRequest | withApplicationName(String applicationName)
 The name of an CodeDeploy application associated with the user or Amazon Web Services account. | 
| CreateDeploymentRequest | withAutoRollbackConfiguration(AutoRollbackConfiguration autoRollbackConfiguration)
 Configuration information for an automatic rollback that is added when a deployment is created. | 
| CreateDeploymentRequest | withDeploymentConfigName(String deploymentConfigName)
 The name of a deployment configuration associated with the user or Amazon Web Services account. | 
| CreateDeploymentRequest | withDeploymentGroupName(String deploymentGroupName)
 The name of the deployment group. | 
| CreateDeploymentRequest | withDescription(String description)
 A comment about the deployment. | 
| CreateDeploymentRequest | withFileExistsBehavior(FileExistsBehavior fileExistsBehavior)
 Information about how CodeDeploy handles files that already exist in a deployment target location but weren't
 part of the previous successful deployment. | 
| CreateDeploymentRequest | withFileExistsBehavior(String fileExistsBehavior)
 Information about how CodeDeploy handles files that already exist in a deployment target location but weren't
 part of the previous successful deployment. | 
| CreateDeploymentRequest | withIgnoreApplicationStopFailures(Boolean ignoreApplicationStopFailures)
 If true, then if an  ApplicationStop,BeforeBlockTraffic, orAfterBlockTrafficdeployment lifecycle event to an instance fails, then the deployment continues to
 the next deployment lifecycle event. | 
| CreateDeploymentRequest | withOverrideAlarmConfiguration(AlarmConfiguration overrideAlarmConfiguration)
 Allows you to specify information about alarms associated with a deployment. | 
| CreateDeploymentRequest | withRevision(RevisionLocation revision)
 The type and location of the revision to deploy. | 
| CreateDeploymentRequest | withTargetInstances(TargetInstances targetInstances)
 Information about the instances that belong to the replacement environment in a blue/green deployment. | 
| CreateDeploymentRequest | withUpdateOutdatedInstancesOnly(Boolean updateOutdatedInstancesOnly)
 Indicates whether to deploy to all instances or only to instances that are not running the latest application
 revision. | 
addHandlerContext, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeoutpublic void setApplicationName(String applicationName)
The name of an CodeDeploy application associated with the user or Amazon Web Services account.
applicationName - The name of an CodeDeploy application associated with the user or Amazon Web Services account.public String getApplicationName()
The name of an CodeDeploy application associated with the user or Amazon Web Services account.
public CreateDeploymentRequest withApplicationName(String applicationName)
The name of an CodeDeploy application associated with the user or Amazon Web Services account.
applicationName - The name of an CodeDeploy application associated with the user or Amazon Web Services account.public void setDeploymentGroupName(String deploymentGroupName)
The name of the deployment group.
deploymentGroupName - The name of the deployment group.public String getDeploymentGroupName()
The name of the deployment group.
public CreateDeploymentRequest withDeploymentGroupName(String deploymentGroupName)
The name of the deployment group.
deploymentGroupName - The name of the deployment group.public void setRevision(RevisionLocation revision)
The type and location of the revision to deploy.
revision - The type and location of the revision to deploy.public RevisionLocation getRevision()
The type and location of the revision to deploy.
public CreateDeploymentRequest withRevision(RevisionLocation revision)
The type and location of the revision to deploy.
revision - The type and location of the revision to deploy.public void setDeploymentConfigName(String deploymentConfigName)
The name of a deployment configuration associated with the user or Amazon Web Services account.
 If not specified, the value configured in the deployment group is used as the default. If the deployment group
 does not have a deployment configuration associated with it, CodeDeployDefault.
 OneAtATime is used by default.
 
deploymentConfigName - The name of a deployment configuration associated with the user or Amazon Web Services account.
        
        If not specified, the value configured in the deployment group is used as the default. If the deployment
        group does not have a deployment configuration associated with it, CodeDeployDefault.
        OneAtATime is used by default.
public String getDeploymentConfigName()
The name of a deployment configuration associated with the user or Amazon Web Services account.
 If not specified, the value configured in the deployment group is used as the default. If the deployment group
 does not have a deployment configuration associated with it, CodeDeployDefault.
 OneAtATime is used by default.
 
         If not specified, the value configured in the deployment group is used as the default. If the deployment
         group does not have a deployment configuration associated with it, CodeDeployDefault.
         OneAtATime is used by default.
public CreateDeploymentRequest withDeploymentConfigName(String deploymentConfigName)
The name of a deployment configuration associated with the user or Amazon Web Services account.
 If not specified, the value configured in the deployment group is used as the default. If the deployment group
 does not have a deployment configuration associated with it, CodeDeployDefault.
 OneAtATime is used by default.
 
deploymentConfigName - The name of a deployment configuration associated with the user or Amazon Web Services account.
        
        If not specified, the value configured in the deployment group is used as the default. If the deployment
        group does not have a deployment configuration associated with it, CodeDeployDefault.
        OneAtATime is used by default.
public void setDescription(String description)
A comment about the deployment.
description - A comment about the deployment.public String getDescription()
A comment about the deployment.
public CreateDeploymentRequest withDescription(String description)
A comment about the deployment.
description - A comment about the deployment.public void setIgnoreApplicationStopFailures(Boolean ignoreApplicationStopFailures)
 If true, then if an ApplicationStop, BeforeBlockTraffic, or
 AfterBlockTraffic deployment lifecycle event to an instance fails, then the deployment continues to
 the next deployment lifecycle event. For example, if ApplicationStop fails, the deployment continues
 with DownloadBundle. If BeforeBlockTraffic fails, the deployment continues with
 BlockTraffic. If AfterBlockTraffic fails, the deployment continues with
 ApplicationStop.
 
If false or not specified, then if a lifecycle event fails during a deployment to an instance, that deployment fails. If deployment to that instance is part of an overall deployment and the number of healthy hosts is not less than the minimum number of healthy hosts, then a deployment to the next instance is attempted.
 During a deployment, the CodeDeploy agent runs the scripts specified for ApplicationStop,
 BeforeBlockTraffic, and AfterBlockTraffic in the AppSpec file from the previous
 successful deployment. (All other scripts are run from the AppSpec file in the current deployment.) If one of
 these scripts contains an error and does not run successfully, the deployment can fail.
 
 If the cause of the failure is a script from the last successful deployment that will never run successfully,
 create a new deployment and use ignoreApplicationStopFailures to specify that the
 ApplicationStop, BeforeBlockTraffic, and AfterBlockTraffic failures should
 be ignored.
 
ignoreApplicationStopFailures - If true, then if an ApplicationStop, BeforeBlockTraffic, or
        AfterBlockTraffic deployment lifecycle event to an instance fails, then the deployment
        continues to the next deployment lifecycle event. For example, if ApplicationStop fails, the
        deployment continues with DownloadBundle. If BeforeBlockTraffic fails, the
        deployment continues with BlockTraffic. If AfterBlockTraffic fails, the
        deployment continues with ApplicationStop. 
        If false or not specified, then if a lifecycle event fails during a deployment to an instance, that deployment fails. If deployment to that instance is part of an overall deployment and the number of healthy hosts is not less than the minimum number of healthy hosts, then a deployment to the next instance is attempted.
        During a deployment, the CodeDeploy agent runs the scripts specified for ApplicationStop,
        BeforeBlockTraffic, and AfterBlockTraffic in the AppSpec file from the previous
        successful deployment. (All other scripts are run from the AppSpec file in the current deployment.) If one
        of these scripts contains an error and does not run successfully, the deployment can fail.
        
        If the cause of the failure is a script from the last successful deployment that will never run
        successfully, create a new deployment and use ignoreApplicationStopFailures to specify that
        the ApplicationStop, BeforeBlockTraffic, and AfterBlockTraffic
        failures should be ignored.
public Boolean getIgnoreApplicationStopFailures()
 If true, then if an ApplicationStop, BeforeBlockTraffic, or
 AfterBlockTraffic deployment lifecycle event to an instance fails, then the deployment continues to
 the next deployment lifecycle event. For example, if ApplicationStop fails, the deployment continues
 with DownloadBundle. If BeforeBlockTraffic fails, the deployment continues with
 BlockTraffic. If AfterBlockTraffic fails, the deployment continues with
 ApplicationStop.
 
If false or not specified, then if a lifecycle event fails during a deployment to an instance, that deployment fails. If deployment to that instance is part of an overall deployment and the number of healthy hosts is not less than the minimum number of healthy hosts, then a deployment to the next instance is attempted.
 During a deployment, the CodeDeploy agent runs the scripts specified for ApplicationStop,
 BeforeBlockTraffic, and AfterBlockTraffic in the AppSpec file from the previous
 successful deployment. (All other scripts are run from the AppSpec file in the current deployment.) If one of
 these scripts contains an error and does not run successfully, the deployment can fail.
 
 If the cause of the failure is a script from the last successful deployment that will never run successfully,
 create a new deployment and use ignoreApplicationStopFailures to specify that the
 ApplicationStop, BeforeBlockTraffic, and AfterBlockTraffic failures should
 be ignored.
 
ApplicationStop, BeforeBlockTraffic, or
         AfterBlockTraffic deployment lifecycle event to an instance fails, then the deployment
         continues to the next deployment lifecycle event. For example, if ApplicationStop fails, the
         deployment continues with DownloadBundle. If BeforeBlockTraffic fails, the
         deployment continues with BlockTraffic. If AfterBlockTraffic fails, the
         deployment continues with ApplicationStop. 
         If false or not specified, then if a lifecycle event fails during a deployment to an instance, that deployment fails. If deployment to that instance is part of an overall deployment and the number of healthy hosts is not less than the minimum number of healthy hosts, then a deployment to the next instance is attempted.
         During a deployment, the CodeDeploy agent runs the scripts specified for ApplicationStop,
         BeforeBlockTraffic, and AfterBlockTraffic in the AppSpec file from the previous
         successful deployment. (All other scripts are run from the AppSpec file in the current deployment.) If
         one of these scripts contains an error and does not run successfully, the deployment can fail.
         
         If the cause of the failure is a script from the last successful deployment that will never run
         successfully, create a new deployment and use ignoreApplicationStopFailures to specify that
         the ApplicationStop, BeforeBlockTraffic, and AfterBlockTraffic
         failures should be ignored.
public CreateDeploymentRequest withIgnoreApplicationStopFailures(Boolean ignoreApplicationStopFailures)
 If true, then if an ApplicationStop, BeforeBlockTraffic, or
 AfterBlockTraffic deployment lifecycle event to an instance fails, then the deployment continues to
 the next deployment lifecycle event. For example, if ApplicationStop fails, the deployment continues
 with DownloadBundle. If BeforeBlockTraffic fails, the deployment continues with
 BlockTraffic. If AfterBlockTraffic fails, the deployment continues with
 ApplicationStop.
 
If false or not specified, then if a lifecycle event fails during a deployment to an instance, that deployment fails. If deployment to that instance is part of an overall deployment and the number of healthy hosts is not less than the minimum number of healthy hosts, then a deployment to the next instance is attempted.
 During a deployment, the CodeDeploy agent runs the scripts specified for ApplicationStop,
 BeforeBlockTraffic, and AfterBlockTraffic in the AppSpec file from the previous
 successful deployment. (All other scripts are run from the AppSpec file in the current deployment.) If one of
 these scripts contains an error and does not run successfully, the deployment can fail.
 
 If the cause of the failure is a script from the last successful deployment that will never run successfully,
 create a new deployment and use ignoreApplicationStopFailures to specify that the
 ApplicationStop, BeforeBlockTraffic, and AfterBlockTraffic failures should
 be ignored.
 
ignoreApplicationStopFailures - If true, then if an ApplicationStop, BeforeBlockTraffic, or
        AfterBlockTraffic deployment lifecycle event to an instance fails, then the deployment
        continues to the next deployment lifecycle event. For example, if ApplicationStop fails, the
        deployment continues with DownloadBundle. If BeforeBlockTraffic fails, the
        deployment continues with BlockTraffic. If AfterBlockTraffic fails, the
        deployment continues with ApplicationStop. 
        If false or not specified, then if a lifecycle event fails during a deployment to an instance, that deployment fails. If deployment to that instance is part of an overall deployment and the number of healthy hosts is not less than the minimum number of healthy hosts, then a deployment to the next instance is attempted.
        During a deployment, the CodeDeploy agent runs the scripts specified for ApplicationStop,
        BeforeBlockTraffic, and AfterBlockTraffic in the AppSpec file from the previous
        successful deployment. (All other scripts are run from the AppSpec file in the current deployment.) If one
        of these scripts contains an error and does not run successfully, the deployment can fail.
        
        If the cause of the failure is a script from the last successful deployment that will never run
        successfully, create a new deployment and use ignoreApplicationStopFailures to specify that
        the ApplicationStop, BeforeBlockTraffic, and AfterBlockTraffic
        failures should be ignored.
public Boolean isIgnoreApplicationStopFailures()
 If true, then if an ApplicationStop, BeforeBlockTraffic, or
 AfterBlockTraffic deployment lifecycle event to an instance fails, then the deployment continues to
 the next deployment lifecycle event. For example, if ApplicationStop fails, the deployment continues
 with DownloadBundle. If BeforeBlockTraffic fails, the deployment continues with
 BlockTraffic. If AfterBlockTraffic fails, the deployment continues with
 ApplicationStop.
 
If false or not specified, then if a lifecycle event fails during a deployment to an instance, that deployment fails. If deployment to that instance is part of an overall deployment and the number of healthy hosts is not less than the minimum number of healthy hosts, then a deployment to the next instance is attempted.
 During a deployment, the CodeDeploy agent runs the scripts specified for ApplicationStop,
 BeforeBlockTraffic, and AfterBlockTraffic in the AppSpec file from the previous
 successful deployment. (All other scripts are run from the AppSpec file in the current deployment.) If one of
 these scripts contains an error and does not run successfully, the deployment can fail.
 
 If the cause of the failure is a script from the last successful deployment that will never run successfully,
 create a new deployment and use ignoreApplicationStopFailures to specify that the
 ApplicationStop, BeforeBlockTraffic, and AfterBlockTraffic failures should
 be ignored.
 
ApplicationStop, BeforeBlockTraffic, or
         AfterBlockTraffic deployment lifecycle event to an instance fails, then the deployment
         continues to the next deployment lifecycle event. For example, if ApplicationStop fails, the
         deployment continues with DownloadBundle. If BeforeBlockTraffic fails, the
         deployment continues with BlockTraffic. If AfterBlockTraffic fails, the
         deployment continues with ApplicationStop. 
         If false or not specified, then if a lifecycle event fails during a deployment to an instance, that deployment fails. If deployment to that instance is part of an overall deployment and the number of healthy hosts is not less than the minimum number of healthy hosts, then a deployment to the next instance is attempted.
         During a deployment, the CodeDeploy agent runs the scripts specified for ApplicationStop,
         BeforeBlockTraffic, and AfterBlockTraffic in the AppSpec file from the previous
         successful deployment. (All other scripts are run from the AppSpec file in the current deployment.) If
         one of these scripts contains an error and does not run successfully, the deployment can fail.
         
         If the cause of the failure is a script from the last successful deployment that will never run
         successfully, create a new deployment and use ignoreApplicationStopFailures to specify that
         the ApplicationStop, BeforeBlockTraffic, and AfterBlockTraffic
         failures should be ignored.
public void setTargetInstances(TargetInstances targetInstances)
Information about the instances that belong to the replacement environment in a blue/green deployment.
targetInstances - Information about the instances that belong to the replacement environment in a blue/green deployment.public TargetInstances getTargetInstances()
Information about the instances that belong to the replacement environment in a blue/green deployment.
public CreateDeploymentRequest withTargetInstances(TargetInstances targetInstances)
Information about the instances that belong to the replacement environment in a blue/green deployment.
targetInstances - Information about the instances that belong to the replacement environment in a blue/green deployment.public void setAutoRollbackConfiguration(AutoRollbackConfiguration autoRollbackConfiguration)
Configuration information for an automatic rollback that is added when a deployment is created.
autoRollbackConfiguration - Configuration information for an automatic rollback that is added when a deployment is created.public AutoRollbackConfiguration getAutoRollbackConfiguration()
Configuration information for an automatic rollback that is added when a deployment is created.
public CreateDeploymentRequest withAutoRollbackConfiguration(AutoRollbackConfiguration autoRollbackConfiguration)
Configuration information for an automatic rollback that is added when a deployment is created.
autoRollbackConfiguration - Configuration information for an automatic rollback that is added when a deployment is created.public void setUpdateOutdatedInstancesOnly(Boolean updateOutdatedInstancesOnly)
Indicates whether to deploy to all instances or only to instances that are not running the latest application revision.
updateOutdatedInstancesOnly - Indicates whether to deploy to all instances or only to instances that are not running the latest
        application revision.public Boolean getUpdateOutdatedInstancesOnly()
Indicates whether to deploy to all instances or only to instances that are not running the latest application revision.
public CreateDeploymentRequest withUpdateOutdatedInstancesOnly(Boolean updateOutdatedInstancesOnly)
Indicates whether to deploy to all instances or only to instances that are not running the latest application revision.
updateOutdatedInstancesOnly - Indicates whether to deploy to all instances or only to instances that are not running the latest
        application revision.public Boolean isUpdateOutdatedInstancesOnly()
Indicates whether to deploy to all instances or only to instances that are not running the latest application revision.
public void setFileExistsBehavior(String fileExistsBehavior)
Information about how CodeDeploy handles files that already exist in a deployment target location but weren't part of the previous successful deployment.
 The fileExistsBehavior parameter takes any of the following values:
 
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
fileExistsBehavior - Information about how CodeDeploy handles files that already exist in a deployment target location but
        weren't part of the previous successful deployment.
        
        The fileExistsBehavior parameter takes any of the following values:
        
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
FileExistsBehaviorpublic String getFileExistsBehavior()
Information about how CodeDeploy handles files that already exist in a deployment target location but weren't part of the previous successful deployment.
 The fileExistsBehavior parameter takes any of the following values:
 
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
         The fileExistsBehavior parameter takes any of the following values:
         
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
FileExistsBehaviorpublic CreateDeploymentRequest withFileExistsBehavior(String fileExistsBehavior)
Information about how CodeDeploy handles files that already exist in a deployment target location but weren't part of the previous successful deployment.
 The fileExistsBehavior parameter takes any of the following values:
 
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
fileExistsBehavior - Information about how CodeDeploy handles files that already exist in a deployment target location but
        weren't part of the previous successful deployment.
        
        The fileExistsBehavior parameter takes any of the following values:
        
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
FileExistsBehaviorpublic void setFileExistsBehavior(FileExistsBehavior fileExistsBehavior)
Information about how CodeDeploy handles files that already exist in a deployment target location but weren't part of the previous successful deployment.
 The fileExistsBehavior parameter takes any of the following values:
 
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
fileExistsBehavior - Information about how CodeDeploy handles files that already exist in a deployment target location but
        weren't part of the previous successful deployment.
        
        The fileExistsBehavior parameter takes any of the following values:
        
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
FileExistsBehaviorpublic CreateDeploymentRequest withFileExistsBehavior(FileExistsBehavior fileExistsBehavior)
Information about how CodeDeploy handles files that already exist in a deployment target location but weren't part of the previous successful deployment.
 The fileExistsBehavior parameter takes any of the following values:
 
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
fileExistsBehavior - Information about how CodeDeploy handles files that already exist in a deployment target location but
        weren't part of the previous successful deployment.
        
        The fileExistsBehavior parameter takes any of the following values:
        
DISALLOW: The deployment fails. This is also the default behavior if no option is specified.
OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.
RETAIN: The version of the file already on the instance is kept and used as part of the new deployment.
FileExistsBehaviorpublic void setOverrideAlarmConfiguration(AlarmConfiguration overrideAlarmConfiguration)
 Allows you to specify information about alarms associated with a deployment. The alarm configuration that you
 specify here will override the alarm configuration at the deployment group level. Consider overriding the alarm
 configuration if you have set up alarms at the deployment group level that are causing deployment failures. In
 this case, you would call CreateDeployment to create a new deployment that uses a previous
 application revision that is known to work, and set its alarm configuration to turn off alarm polling. Turning
 off alarm polling ensures that the new deployment proceeds without being blocked by the alarm that was generated
 by the previous, failed, deployment.
 
 If you specify an overrideAlarmConfiguration, you need the UpdateDeploymentGroup IAM
 permission when calling CreateDeployment.
 
overrideAlarmConfiguration - Allows you to specify information about alarms associated with a deployment. The alarm configuration that
        you specify here will override the alarm configuration at the deployment group level. Consider overriding
        the alarm configuration if you have set up alarms at the deployment group level that are causing
        deployment failures. In this case, you would call CreateDeployment to create a new deployment
        that uses a previous application revision that is known to work, and set its alarm configuration to turn
        off alarm polling. Turning off alarm polling ensures that the new deployment proceeds without being
        blocked by the alarm that was generated by the previous, failed, deployment. 
        If you specify an overrideAlarmConfiguration, you need the UpdateDeploymentGroup
        IAM permission when calling CreateDeployment.
        
public AlarmConfiguration getOverrideAlarmConfiguration()
 Allows you to specify information about alarms associated with a deployment. The alarm configuration that you
 specify here will override the alarm configuration at the deployment group level. Consider overriding the alarm
 configuration if you have set up alarms at the deployment group level that are causing deployment failures. In
 this case, you would call CreateDeployment to create a new deployment that uses a previous
 application revision that is known to work, and set its alarm configuration to turn off alarm polling. Turning
 off alarm polling ensures that the new deployment proceeds without being blocked by the alarm that was generated
 by the previous, failed, deployment.
 
 If you specify an overrideAlarmConfiguration, you need the UpdateDeploymentGroup IAM
 permission when calling CreateDeployment.
 
CreateDeployment to create a new
         deployment that uses a previous application revision that is known to work, and set its alarm
         configuration to turn off alarm polling. Turning off alarm polling ensures that the new deployment
         proceeds without being blocked by the alarm that was generated by the previous, failed, deployment.
         
         If you specify an overrideAlarmConfiguration, you need the
         UpdateDeploymentGroup IAM permission when calling CreateDeployment.
         
public CreateDeploymentRequest withOverrideAlarmConfiguration(AlarmConfiguration overrideAlarmConfiguration)
 Allows you to specify information about alarms associated with a deployment. The alarm configuration that you
 specify here will override the alarm configuration at the deployment group level. Consider overriding the alarm
 configuration if you have set up alarms at the deployment group level that are causing deployment failures. In
 this case, you would call CreateDeployment to create a new deployment that uses a previous
 application revision that is known to work, and set its alarm configuration to turn off alarm polling. Turning
 off alarm polling ensures that the new deployment proceeds without being blocked by the alarm that was generated
 by the previous, failed, deployment.
 
 If you specify an overrideAlarmConfiguration, you need the UpdateDeploymentGroup IAM
 permission when calling CreateDeployment.
 
overrideAlarmConfiguration - Allows you to specify information about alarms associated with a deployment. The alarm configuration that
        you specify here will override the alarm configuration at the deployment group level. Consider overriding
        the alarm configuration if you have set up alarms at the deployment group level that are causing
        deployment failures. In this case, you would call CreateDeployment to create a new deployment
        that uses a previous application revision that is known to work, and set its alarm configuration to turn
        off alarm polling. Turning off alarm polling ensures that the new deployment proceeds without being
        blocked by the alarm that was generated by the previous, failed, deployment. 
        If you specify an overrideAlarmConfiguration, you need the UpdateDeploymentGroup
        IAM permission when calling CreateDeployment.
        
public String toString()
toString in class ObjectObject.toString()public CreateDeploymentRequest clone()
AmazonWebServiceRequestclone in class AmazonWebServiceRequestObject.clone()