pulumi-google-native-kotlin/com.pulumi.googlenative.gkebackup.v1.kotlin.outputs/GetBackupPlanResult

GetBackupPlanResult

data class GetBackupPlanResult(val backupConfig: BackupConfigResponse, val backupSchedule: ScheduleResponse, val cluster: String, val createTime: String, val deactivated: Boolean, val description: String, val etag: String, val labels: Map<String, String>, val name: String, val protectedPodCount: Int, val retentionPolicy: RetentionPolicyResponse, val uid: String, val updateTime: String)

Constructors

GetBackupPlanResult

fun GetBackupPlanResult(backupConfig: BackupConfigResponse, backupSchedule: ScheduleResponse, cluster: String, createTime: String, deactivated: Boolean, description: String, etag: String, labels: Map<String, String>, name: String, protectedPodCount: Int, retentionPolicy: RetentionPolicyResponse, uid: String, updateTime: String)

Types

Companion

object Companion

Properties

backupConfig

val backupConfig: BackupConfigResponse

Defines the configuration of Backups created via this BackupPlan.

backupSchedule

val backupSchedule: ScheduleResponse

Defines a schedule for automatic Backup creation via this BackupPlan.

cluster

val cluster: String

Immutable. The source cluster from which Backups will be created via this BackupPlan. Valid formats: - projects/*/locations/*/clusters/* - projects/*/zones/*/clusters/*

createTime

val createTime: String

The timestamp when this BackupPlan resource was created.

deactivated

val deactivated: Boolean

This flag indicates whether this BackupPlan has been deactivated. Setting this field to True locks the BackupPlan such that no further updates will be allowed (except deletes), including the deactivated field itself. It also prevents any new Backups from being created via this BackupPlan (including scheduled Backups). Default: False

description

val description: String

User specified descriptive string for this BackupPlan.

etag

val etag: String

etag is used for optimistic concurrency control as a way to help prevent simultaneous updates of a backup plan from overwriting each other. It is strongly suggested that systems make use of the 'etag' in the read-modify-write cycle to perform BackupPlan updates in order to avoid race conditions: An etag is returned in the response to GetBackupPlan, and systems are expected to put that etag in the request to UpdateBackupPlan or DeleteBackupPlan to ensure that their change will be applied to the same version of the resource.

labels