Class RestoreClusterRequest (0.4.1) 

RestoreClusterRequest(mapping=None, *, ignore_unknown_fields=False, **kwargs)

Message for restoring a Cluster from a backup or another cluster at a given point in time.

This message has oneof_ fields (mutually exclusive fields). For each oneof, at most one member field can be set at the same time. Setting any member of the oneof automatically clears all other members.

.. _oneof: https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields

Attributes
Name Description
backup_source google.cloud.alloydb_v1beta.types.BackupSource
Backup source. This field is a member of oneof_ source.
continuous_backup_source google.cloud.alloydb_v1beta.types.ContinuousBackupSource
ContinuousBackup source. Continuous backup needs to be enabled in the source cluster for this operation to succeed. This field is a member of oneof_ source.
parent str
Required. The name of the parent resource. For the required format, see the comment on the Cluster.name field.
cluster_id str
Required. ID of the requesting object.
cluster google.cloud.alloydb_v1beta.types.Cluster
Required. The resource being created
request_id str
Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server ignores the request if it has already been completed. The server guarantees that for at least 60 minutes since the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if the original operation with the same request ID was received, and if so, ignores the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
validate_only bool
Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.