Enum RestoreConfig.NamespacedResourceRestoreMode

java.lang.Object
java.lang.Enum<RestoreConfig.NamespacedResourceRestoreMode>
com.google.cloud.gkebackup.v1.RestoreConfig.NamespacedResourceRestoreMode
All Implemented Interfaces:
com.google.protobuf.Internal.EnumLite, com.google.protobuf.ProtocolMessageEnum, Serializable, Comparable<RestoreConfig.NamespacedResourceRestoreMode>
Enclosing class:
RestoreConfig

public static enum RestoreConfig.NamespacedResourceRestoreMode extends Enum<RestoreConfig.NamespacedResourceRestoreMode> implements com.google.protobuf.ProtocolMessageEnum
 Defines the behavior for handling the situation where sets of namespaced
 resources being restored already exist in the target cluster.
 
Protobuf enum google.cloud.gkebackup.v1.RestoreConfig.NamespacedResourceRestoreMode
  • Enum Constant Details

    • NAMESPACED_RESOURCE_RESTORE_MODE_UNSPECIFIED

      public static final RestoreConfig.NamespacedResourceRestoreMode NAMESPACED_RESOURCE_RESTORE_MODE_UNSPECIFIED
       Unspecified (invalid).
       
      NAMESPACED_RESOURCE_RESTORE_MODE_UNSPECIFIED = 0;
    • DELETE_AND_RESTORE

      public static final RestoreConfig.NamespacedResourceRestoreMode DELETE_AND_RESTORE
       When conflicting top-level resources (either Namespaces or
       ProtectedApplications, depending upon the scope) are encountered, this
       will first trigger a delete of the conflicting resource AND ALL OF ITS
       REFERENCED RESOURCES (e.g., all resources in the Namespace or all
       resources referenced by the ProtectedApplication) before restoring the
       resources from the Backup. This mode should only be used when you are
       intending to revert some portion of a cluster to an earlier state.
       
      DELETE_AND_RESTORE = 1;
    • FAIL_ON_CONFLICT

      public static final RestoreConfig.NamespacedResourceRestoreMode FAIL_ON_CONFLICT
       If conflicting top-level resources (either Namespaces or
       ProtectedApplications, depending upon the scope) are encountered at the
       beginning of a restore process, the Restore will fail.  If a conflict
       occurs during the restore process itself (e.g., because an out of band
       process creates conflicting resources), a conflict will be reported.
       
      FAIL_ON_CONFLICT = 2;
    • MERGE_SKIP_ON_CONFLICT

      public static final RestoreConfig.NamespacedResourceRestoreMode 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.
       
      MERGE_SKIP_ON_CONFLICT = 3;
    • MERGE_REPLACE_VOLUME_ON_CONFLICT

      public static final RestoreConfig.NamespacedResourceRestoreMode 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_REPLACE_VOLUME_ON_CONFLICT = 4;
    • MERGE_REPLACE_ON_CONFLICT

      public static final RestoreConfig.NamespacedResourceRestoreMode 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_ON_CONFLICT = 5;
    • UNRECOGNIZED

      public static final RestoreConfig.NamespacedResourceRestoreMode UNRECOGNIZED
  • Field Details

    • NAMESPACED_RESOURCE_RESTORE_MODE_UNSPECIFIED_VALUE

      public static final int NAMESPACED_RESOURCE_RESTORE_MODE_UNSPECIFIED_VALUE
       Unspecified (invalid).
       
      NAMESPACED_RESOURCE_RESTORE_MODE_UNSPECIFIED = 0;
      See Also:
    • DELETE_AND_RESTORE_VALUE

      public static final int DELETE_AND_RESTORE_VALUE
       When conflicting top-level resources (either Namespaces or
       ProtectedApplications, depending upon the scope) are encountered, this
       will first trigger a delete of the conflicting resource AND ALL OF ITS
       REFERENCED RESOURCES (e.g., all resources in the Namespace or all
       resources referenced by the ProtectedApplication) before restoring the
       resources from the Backup. This mode should only be used when you are
       intending to revert some portion of a cluster to an earlier state.
       
      DELETE_AND_RESTORE = 1;
      See Also:
    • FAIL_ON_CONFLICT_VALUE

      public static final int FAIL_ON_CONFLICT_VALUE
       If conflicting top-level resources (either Namespaces or
       ProtectedApplications, depending upon the scope) are encountered at the
       beginning of a restore process, the Restore will fail.  If a conflict
       occurs during the restore process itself (e.g., because an out of band
       process creates conflicting resources), a conflict will be reported.
       
      FAIL_ON_CONFLICT = 2;
      See Also:
    • MERGE_SKIP_ON_CONFLICT_VALUE

      public static final int MERGE_SKIP_ON_CONFLICT_VALUE
       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.
       
      MERGE_SKIP_ON_CONFLICT = 3;
      See Also:
    • MERGE_REPLACE_VOLUME_ON_CONFLICT_VALUE

      public static final int MERGE_REPLACE_VOLUME_ON_CONFLICT_VALUE
       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_REPLACE_VOLUME_ON_CONFLICT = 4;
      See Also:
    • MERGE_REPLACE_ON_CONFLICT_VALUE

      public static final int MERGE_REPLACE_ON_CONFLICT_VALUE
       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_ON_CONFLICT = 5;
      See Also:
  • Method Details

    • values

      Returns an array containing the constants of this enum type, in the order they are declared.
      Returns:
      an array containing the constants of this enum type, in the order they are declared
    • valueOf

      Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
      Parameters:
      name - the name of the enum constant to be returned.
      Returns:
      the enum constant with the specified name
      Throws:
      IllegalArgumentException - if this enum type has no constant with the specified name
      NullPointerException - if the argument is null
    • getNumber

      public final int getNumber()
      Specified by:
      getNumber in interface com.google.protobuf.Internal.EnumLite
      Specified by:
      getNumber in interface com.google.protobuf.ProtocolMessageEnum
    • valueOf

      @Deprecated public static RestoreConfig.NamespacedResourceRestoreMode valueOf(int value)
      Deprecated.
      Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
      Parameters:
      value - the name of the enum constant to be returned.
      Returns:
      the enum constant with the specified name
      Throws:
      IllegalArgumentException - if this enum type has no constant with the specified name
      NullPointerException - if the argument is null
    • forNumber

      public static RestoreConfig.NamespacedResourceRestoreMode forNumber(int value)
      Parameters:
      value - The numeric wire value of the corresponding enum entry.
      Returns:
      The enum associated with the given numeric wire value.
    • internalGetValueMap

      public static com.google.protobuf.Internal.EnumLiteMap<RestoreConfig.NamespacedResourceRestoreMode> internalGetValueMap()
    • getValueDescriptor

      public final com.google.protobuf.Descriptors.EnumValueDescriptor getValueDescriptor()
      Specified by:
      getValueDescriptor in interface com.google.protobuf.ProtocolMessageEnum
    • getDescriptorForType

      public final com.google.protobuf.Descriptors.EnumDescriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.ProtocolMessageEnum
    • getDescriptor

      public static com.google.protobuf.Descriptors.EnumDescriptor getDescriptor()
    • valueOf

      public static RestoreConfig.NamespacedResourceRestoreMode valueOf(com.google.protobuf.Descriptors.EnumValueDescriptor desc)
      Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
      Parameters:
      desc - the name of the enum constant to be returned.
      Returns:
      the enum constant with the specified name
      Throws:
      IllegalArgumentException - if this enum type has no constant with the specified name
      NullPointerException - if the argument is null