gcloud: Thu May 30 09:26:18 UTC 2024

gcloud/beta/container/backup-restore/restore-plans/create

@@ -12,8 +12,10 @@ SYNOPSIS
         [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY]
         [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
         [--namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE]
+        [--restore-order-file=RESTORE_ORDER_FILE]
         [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY;
           default="no-volume-data-restoration"]
+        [--volume-data-restore-policy-bindings=[VOLUME_TYPE=POLICY,...]]
         [--cluster-resource-scope-all-group-kinds
           | --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS,
           ...] | --cluster-resource-scope-no-group-kinds
@@ -173,6 +175,45 @@ OPTIONAL FLAGS
             out of band process creates conflicting resources), a conflict will
             be reported.
 
+         merge-replace-on-conflict
+            This mode merges the backup and the target cluster and replaces the
+            conflicting resources with the ones in the backup. If a single
+            resource to restore exists in the cluster before restoration, the
+            resource will be replaced with the one from the backup. To replace
+            an existing resource, the first attempt is to update the resource
+            to match the one from the backup; if the update fails, the second
+            attempt is to delete the resource and restore it from the backup.
+            Note that this mode could cause data loss as it replaces the
+            existing resources in the target cluster, and the original PV can
+            be retained or deleted depending on its reclaim policy.
+
+         merge-replace-volume-on-conflict
+            This mode merges the backup and the target cluster and skips the
+            conflicting resources except volume data. If a PVC to restore
+            already exists, this mode will restore/reconnect the volume without
+            overwriting the PVC. It is similar to MERGE_SKIP_ON_CONFLICT except
+            that it will apply the volume data policy for the conflicting PVCs
+            "RESTORE_VOLUME_DATA_FROM_BACKUP:" restore data only and respect
+            the reclaim policy of the original PV;
+            "REUSE_VOLUME_HANDLE_FROM_BACKUP:" reconnect and respect the
+            reclaim policy of the original PV; "NO_VOLUME_DATA_RESTORATION:"
+            new provision and respect the reclaim policy of the original PV.
+            Note that this mode could cause data loss as the original PV can be
+            retained or deleted depending on its reclaim policy.
+
+         merge-skip-on-conflict
+            This mode merges the backup and the target cluster and skips the
+            conflicting resources. If a single resource to restore exists in
+            the cluster before restoration, the resource will be skipped,
+            otherwise it will be restored.
+
+     --restore-order-file=RESTORE_ORDER_FILE
+        If provided, defines a custom order that can be used in a restore,
+        which includes dependencies between two group kinds that must be
+        honored during a restore, a satisfying group kind and a requiring group
+        kind. The satisfying group kind must be restored before the requiring
+        group kind.
+
      --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration"
         Define how data is populated for restored volumes. If this flag is not
         specified, 'no-volume-data-restoration' will be used.
@@ -194,6 +235,12 @@ OPTIONAL FLAGS
             pre-provisioned using the volume handle of the original PV in the
             Backup.
 
+     --volume-data-restore-policy-bindings=[VOLUME_TYPE=POLICY,...]
+        Dict that binds a supported volume type to a volume data restore
+        policy. e.g. gce-persistent-disk=restore-volume-data-from-backup for a
+        binding that results in Persistent Disk volumes being restored using
+        the "restore volume data from backup" policy.
+
      The scope of cluster-scoped resources to restore.
 
      At most one of these can be specified:
@@ -221,9 +268,12 @@ OPTIONAL FLAGS
      At most one of these can be specified:
 
        --substitution-rules-file=SUBSTITUTION_RULES_FILE
-          If provided, defines a set of resource transformations that will be
-          applied to resources from the source backup before they are created
-          in the target cluster.
+          (DEPRECATED) If provided, defines a set of resource transformations
+          that will be applied to resources from the source backup before they
+          are created in the target cluster.
+
+          Flag substitution-rules-file is deprecated. Please use
+          --transformation-rules-file instead.
 
        --transformation-rules-file=TRANSFORMATION_RULES_FILE
           If provided, defines a set of resource transformations that will be