Struct aws_sdk_codedeploy::operation::create_deployment::builders::CreateDeploymentFluentBuilder

source ·

pub struct CreateDeploymentFluentBuilder { /* private fields */ }

Expand description

Fluent builder constructing a request to CreateDeployment.

Deploys an application revision through the specified deployment group.

Implementations§

source §

impl CreateDeploymentFluentBuilder

source

pub fn as_input(&self) -> &CreateDeploymentInputBuilder

Access the CreateDeployment as a reference.

source

pub async fn send( self ) -> Result<CreateDeploymentOutput, SdkError<CreateDeploymentError, HttpResponse>>

Sends the request and returns the response.

If an error occurs, an SdkError will be returned with additional details that can be matched against.

By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.

source

pub fn customize( self ) -> CustomizableOperation<CreateDeploymentOutput, CreateDeploymentError, Self>

Consumes this builder, creating a customizable operation that can be modified before being sent.

source

pub fn application_name(self, input: impl Into<String>) -> Self

The name of an CodeDeploy application associated with the user or Amazon Web Services account.

source

pub fn set_application_name(self, input: Option<String>) -> Self

The name of an CodeDeploy application associated with the user or Amazon Web Services account.

source

pub fn get_application_name(&self) -> &Option<String>

The name of an CodeDeploy application associated with the user or Amazon Web Services account.

source

pub fn deployment_group_name(self, input: impl Into<String>) -> Self

The name of the deployment group.

source

pub fn set_deployment_group_name(self, input: Option<String>) -> Self

The name of the deployment group.

source

pub fn get_deployment_group_name(&self) -> &Option<String>

The name of the deployment group.

source

pub fn revision(self, input: RevisionLocation) -> Self

The type and location of the revision to deploy.

source

pub fn set_revision(self, input: Option<RevisionLocation>) -> Self

The type and location of the revision to deploy.

source

pub fn get_revision(&self) -> &Option<RevisionLocation>

The type and location of the revision to deploy.

source

pub fn deployment_config_name(self, input: impl Into<String>) -> Self

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.

source

pub fn set_deployment_config_name(self, input: Option<String>) -> Self

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.

source

pub fn get_deployment_config_name(&self) -> &Option<String>

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.

source

pub fn description(self, input: impl Into<String>) -> Self

A comment about the deployment.

source

pub fn set_description(self, input: Option<String>) -> Self

A comment about the deployment.

source

pub fn get_description(&self) -> &Option<String>

A comment about the deployment.

source

pub fn ignore_application_stop_failures(self, input: bool) -> Self

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.

source

pub fn set_ignore_application_stop_failures(self, input: Option<bool>) -> Self

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.

source

pub fn get_ignore_application_stop_failures(&self) -> &Option<bool>

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.

source

pub fn target_instances(self, input: TargetInstances) -> Self

Information about the instances that belong to the replacement environment in a blue/green deployment.

source

pub fn set_target_instances(self, input: Option<TargetInstances>) -> Self

Information about the instances that belong to the replacement environment in a blue/green deployment.

source

pub fn get_target_instances(&self) -> &Option<TargetInstances>

Information about the instances that belong to the replacement environment in a blue/green deployment.

source

pub fn auto_rollback_configuration( self, input: AutoRollbackConfiguration ) -> Self

Configuration information for an automatic rollback that is added when a deployment is created.

source

pub fn set_auto_rollback_configuration( self, input: Option<AutoRollbackConfiguration> ) -> Self

Configuration information for an automatic rollback that is added when a deployment is created.

source

pub fn get_auto_rollback_configuration( &self ) -> &Option<AutoRollbackConfiguration>

Configuration information for an automatic rollback that is added when a deployment is created.

source

pub fn update_outdated_instances_only(self, input: bool) -> Self

Indicates whether to deploy to all instances or only to instances that are not running the latest application revision.

source

pub fn set_update_outdated_instances_only(self, input: Option<bool>) -> Self

Indicates whether to deploy to all instances or only to instances that are not running the latest application revision.

source

pub fn get_update_outdated_instances_only(&self) -> &Option<bool>

Indicates whether to deploy to all instances or only to instances that are not running the latest application revision.

source

pub fn file_exists_behavior(self, input: FileExistsBehavior) -> Self

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.

source

pub fn set_file_exists_behavior(self, input: Option<FileExistsBehavior>) -> Self

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.

source

pub fn get_file_exists_behavior(&self) -> &Option<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.

source

pub fn override_alarm_configuration(self, input: AlarmConfiguration) -> Self

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.

source

pub fn set_override_alarm_configuration( self, input: Option<AlarmConfiguration> ) -> Self

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.

source

pub fn get_override_alarm_configuration(&self) -> &Option<AlarmConfiguration>

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.