
com.pulumi.googlenative.osconfig.v1beta.kotlin.inputs.PatchRolloutArgs.kt Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of pulumi-google-native-kotlin Show documentation
Show all versions of pulumi-google-native-kotlin Show documentation
Build cloud applications and infrastructure by combining the safety and reliability of infrastructure as code with the power of the Kotlin programming language.
The newest version!
@file:Suppress("NAME_SHADOWING", "DEPRECATION")
package com.pulumi.googlenative.osconfig.v1beta.kotlin.inputs
import com.pulumi.core.Output
import com.pulumi.core.Output.of
import com.pulumi.googlenative.osconfig.v1beta.inputs.PatchRolloutArgs.builder
import com.pulumi.googlenative.osconfig.v1beta.kotlin.enums.PatchRolloutMode
import com.pulumi.kotlin.ConvertibleToJava
import com.pulumi.kotlin.PulumiTagMarker
import com.pulumi.kotlin.applySuspend
import kotlin.Suppress
import kotlin.Unit
import kotlin.jvm.JvmName
/**
* Patch rollout configuration specifications. Contains details on the concurrency control when applying patch(es) to all targeted VMs.
* @property disruptionBudget The maximum number (or percentage) of VMs per zone to disrupt at any given moment. The number of VMs calculated from multiplying the percentage by the total number of VMs in a zone is rounded up. During patching, a VM is considered disrupted from the time the agent is notified to begin until patching has completed. This disruption time includes the time to complete reboot and any post-patch steps. A VM contributes to the disruption budget if its patching operation fails either when applying the patches, running pre or post patch steps, or if it fails to respond with a success notification before timing out. VMs that are not running or do not have an active agent do not count toward this disruption budget. For zone-by-zone rollouts, if the disruption budget in a zone is exceeded, the patch job stops, because continuing to the next zone requires completion of the patch process in the previous zone. For example, if the disruption budget has a fixed value of `10`, and 8 VMs fail to patch in the current zone, the patch job continues to patch 2 VMs at a time until the zone is completed. When that zone is completed successfully, patching begins with 10 VMs at a time in the next zone. If 10 VMs in the next zone fail to patch, the patch job stops.
* @property mode Mode of the patch rollout.
*/
public data class PatchRolloutArgs(
public val disruptionBudget: Output? = null,
public val mode: Output? = null,
) : ConvertibleToJava {
override fun toJava(): com.pulumi.googlenative.osconfig.v1beta.inputs.PatchRolloutArgs =
com.pulumi.googlenative.osconfig.v1beta.inputs.PatchRolloutArgs.builder()
.disruptionBudget(disruptionBudget?.applyValue({ args0 -> args0.let({ args0 -> args0.toJava() }) }))
.mode(mode?.applyValue({ args0 -> args0.let({ args0 -> args0.toJava() }) })).build()
}
/**
* Builder for [PatchRolloutArgs].
*/
@PulumiTagMarker
public class PatchRolloutArgsBuilder internal constructor() {
private var disruptionBudget: Output? = null
private var mode: Output? = null
/**
* @param value The maximum number (or percentage) of VMs per zone to disrupt at any given moment. The number of VMs calculated from multiplying the percentage by the total number of VMs in a zone is rounded up. During patching, a VM is considered disrupted from the time the agent is notified to begin until patching has completed. This disruption time includes the time to complete reboot and any post-patch steps. A VM contributes to the disruption budget if its patching operation fails either when applying the patches, running pre or post patch steps, or if it fails to respond with a success notification before timing out. VMs that are not running or do not have an active agent do not count toward this disruption budget. For zone-by-zone rollouts, if the disruption budget in a zone is exceeded, the patch job stops, because continuing to the next zone requires completion of the patch process in the previous zone. For example, if the disruption budget has a fixed value of `10`, and 8 VMs fail to patch in the current zone, the patch job continues to patch 2 VMs at a time until the zone is completed. When that zone is completed successfully, patching begins with 10 VMs at a time in the next zone. If 10 VMs in the next zone fail to patch, the patch job stops.
*/
@JvmName("mensyacakamlwrhh")
public suspend fun disruptionBudget(`value`: Output) {
this.disruptionBudget = value
}
/**
* @param value Mode of the patch rollout.
*/
@JvmName("gojavjhkdocjcfkr")
public suspend fun mode(`value`: Output) {
this.mode = value
}
/**
* @param value The maximum number (or percentage) of VMs per zone to disrupt at any given moment. The number of VMs calculated from multiplying the percentage by the total number of VMs in a zone is rounded up. During patching, a VM is considered disrupted from the time the agent is notified to begin until patching has completed. This disruption time includes the time to complete reboot and any post-patch steps. A VM contributes to the disruption budget if its patching operation fails either when applying the patches, running pre or post patch steps, or if it fails to respond with a success notification before timing out. VMs that are not running or do not have an active agent do not count toward this disruption budget. For zone-by-zone rollouts, if the disruption budget in a zone is exceeded, the patch job stops, because continuing to the next zone requires completion of the patch process in the previous zone. For example, if the disruption budget has a fixed value of `10`, and 8 VMs fail to patch in the current zone, the patch job continues to patch 2 VMs at a time until the zone is completed. When that zone is completed successfully, patching begins with 10 VMs at a time in the next zone. If 10 VMs in the next zone fail to patch, the patch job stops.
*/
@JvmName("xdnifbbrmctquumq")
public suspend fun disruptionBudget(`value`: FixedOrPercentArgs?) {
val toBeMapped = value
val mapped = toBeMapped?.let({ args0 -> of(args0) })
this.disruptionBudget = mapped
}
/**
* @param argument The maximum number (or percentage) of VMs per zone to disrupt at any given moment. The number of VMs calculated from multiplying the percentage by the total number of VMs in a zone is rounded up. During patching, a VM is considered disrupted from the time the agent is notified to begin until patching has completed. This disruption time includes the time to complete reboot and any post-patch steps. A VM contributes to the disruption budget if its patching operation fails either when applying the patches, running pre or post patch steps, or if it fails to respond with a success notification before timing out. VMs that are not running or do not have an active agent do not count toward this disruption budget. For zone-by-zone rollouts, if the disruption budget in a zone is exceeded, the patch job stops, because continuing to the next zone requires completion of the patch process in the previous zone. For example, if the disruption budget has a fixed value of `10`, and 8 VMs fail to patch in the current zone, the patch job continues to patch 2 VMs at a time until the zone is completed. When that zone is completed successfully, patching begins with 10 VMs at a time in the next zone. If 10 VMs in the next zone fail to patch, the patch job stops.
*/
@JvmName("kfpwpgqemfikwiqn")
public suspend fun disruptionBudget(argument: suspend FixedOrPercentArgsBuilder.() -> Unit) {
val toBeMapped = FixedOrPercentArgsBuilder().applySuspend { argument() }.build()
val mapped = of(toBeMapped)
this.disruptionBudget = mapped
}
/**
* @param value Mode of the patch rollout.
*/
@JvmName("atmnoeolwelkgtio")
public suspend fun mode(`value`: PatchRolloutMode?) {
val toBeMapped = value
val mapped = toBeMapped?.let({ args0 -> of(args0) })
this.mode = mapped
}
internal fun build(): PatchRolloutArgs = PatchRolloutArgs(
disruptionBudget = disruptionBudget,
mode = mode,
)
}
© 2015 - 2025 Weber Informatics LLC | Privacy Policy