pulumi-aws-kotlin/com.pulumi.aws.codedeploy.kotlin.outputs/DeploymentConfigZonalConfig

DeploymentConfigZonalConfig

data class DeploymentConfigZonalConfig(val firstZoneMonitorDurationInSeconds: Int? = null, val minimumHealthyHostsPerZone: DeploymentConfigZonalConfigMinimumHealthyHostsPerZone? = null, val monitorDurationInSeconds: Int? = null)

Constructors

constructor(firstZoneMonitorDurationInSeconds: Int? = null, minimumHealthyHostsPerZone: DeploymentConfigZonalConfigMinimumHealthyHostsPerZone? = null, monitorDurationInSeconds: Int? = null)

Types

Companion

object Companion

Properties

firstZoneMonitorDurationInSeconds

val firstZoneMonitorDurationInSeconds: Int? = null

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.

minimumHealthyHostsPerZone

val minimumHealthyHostsPerZone: DeploymentConfigZonalConfigMinimumHealthyHostsPerZone? = null

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.

monitorDurationInSeconds

val monitorDurationInSeconds: 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.