InstanceGroupManagerInstanceLifecyclePolicyArgs

data class InstanceGroupManagerInstanceLifecyclePolicyArgs(val defaultActionOnFailure: Output<InstanceGroupManagerInstanceLifecyclePolicyDefaultActionOnFailure>? = null, val forceUpdateOnRepair: Output<InstanceGroupManagerInstanceLifecyclePolicyForceUpdateOnRepair>? = null, val metadataBasedReadinessSignal: Output<InstanceGroupManagerInstanceLifecyclePolicyMetadataBasedReadinessSignalArgs>? = null) : ConvertibleToJava<InstanceGroupManagerInstanceLifecyclePolicyArgs>

Constructors

Functions

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

Properties

Link copied to clipboard

Defines behaviour for all instance or failures

Link copied to clipboard

A bit indicating whether to forcefully apply the group's latest configuration when repairing a VM. Valid options are: - NO (default): If configuration updates are available, they are not forcefully applied during repair. Instead, configuration updates are applied according to the group's update policy. - YES: If configuration updates are available, they are applied during repair.

Link copied to clipboard

The configuration for metadata based readiness signal sent by the instance during initialization when stopping / suspending an instance. The Instance Group Manager will wait for a signal that indicates successful initialization before stopping / suspending an instance. If a successful readiness signal is not sent before timeout, the corresponding instance will not be stopped / suspended. Instead, an error will be visible in the lastAttempt.errors field of the managed instance in the listmanagedinstances method. If metadataBasedReadinessSignal.timeoutSec is unset, the Instance Group Manager will directly proceed to suspend / stop instances, skipping initialization on them.