DeploymentConfigZonalConfigArgs

data class DeploymentConfigZonalConfigArgs(val firstZoneMonitorDurationInSeconds: Output<Int>? = null, val minimumHealthyHostsPerZone: Output<DeploymentConfigZonalConfigMinimumHealthyHostsPerZoneArgs>? = null, val monitorDurationInSeconds: Output<Int>? = null) : ConvertibleToJava<DeploymentConfigZonalConfigArgs>

Constructors

Link copied to clipboard
constructor(firstZoneMonitorDurationInSeconds: Output<Int>? = null, minimumHealthyHostsPerZone: Output<DeploymentConfigZonalConfigMinimumHealthyHostsPerZoneArgs>? = null, monitorDurationInSeconds: Output<Int>? = null)

Properties

Link copied to clipboard

The period of time, in seconds, that CodeDeploy must wait after completing a deployment to the first Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the second Availability Zone. If you don't specify a value for first_zone_monitor_duration_in_seconds, then CodeDeploy uses the monitor_duration_in_seconds value for the first Availability Zone.

Link copied to clipboard

The number or percentage of instances that must remain available per Availability Zone during a deployment. If you don't specify a value under minimum_healthy_hosts_per_zone, then CodeDeploy uses a default value of 0 percent. This block is more documented below.

Link copied to clipboard
val monitorDurationInSeconds: Output<Int>? = null

The period of time, in seconds, that CodeDeploy must wait after completing a deployment to an Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the next Availability Zone. If you don't specify a monitor_duration_in_seconds, CodeDeploy starts deploying to the next Availability Zone immediately.

Functions

Link copied to clipboard
open override fun toJava(): DeploymentConfigZonalConfigArgs