@googleapis/alloydb 11.1.0 → 11.3.0

package/v1alpha.ts

@@ -254,6 +254,10 @@ export namespace alloydb_v1alpha {
      * Output only. The current state of the backup.
      */
     state?: string | null;
+    /**
+     * Optional. Input only. Immutable. Tag keys/values directly bound to this resource. For example: ``` "123/environment": "production", "123/costCenter": "marketing" ```
+     */
+    tags?: {[key: string]: string} | null;
     /**
      * The backup type, which suggests the trigger for the backup.
      */
@@ -293,7 +297,7 @@ export namespace alloydb_v1alpha {
      */
     requireConnectors?: boolean | null;
     /**
-     * Optional. SSL config option for this instance.
+     * Optional. SSL configuration option for this instance.
      */
     sslConfig?: Schema$SslConfig;
   }
@@ -456,6 +460,10 @@ export namespace alloydb_v1alpha {
      * Optional. Subscription type of the cluster.
      */
     subscriptionType?: string | null;
+    /**
+     * Optional. Input only. Immutable. Tag keys/values directly bound to this resource. For example: ``` "123/environment": "production", "123/costCenter": "marketing" ```
+     */
+    tags?: {[key: string]: string} | null;
     /**
      * Output only. Metadata for free trial clusters
      */
@@ -578,6 +586,27 @@ export namespace alloydb_v1alpha {
      */
     pointInTime?: string | null;
   }
+  /**
+   * Options for exporting data in CSV format.
+   */
+  export interface Schema$CsvExportOptions {
+    /**
+     * Optional. Specifies the character that should appear before a data character that needs to be escaped. The default is the same as quote character. The value of this argument has to be a character in Hex ASCII Code.
+     */
+    escapeCharacter?: string | null;
+    /**
+     * Optional. Specifies the character that separates columns within each row (line) of the file. The default is comma. The value of this argument has to be a character in Hex ASCII Code.
+     */
+    fieldDelimiter?: string | null;
+    /**
+     * Optional. Specifies the quoting character to be used when a data value is quoted. The default is double-quote. The value of this argument has to be a character in Hex ASCII Code.
+     */
+    quoteCharacter?: string | null;
+    /**
+     * Required. The SELECT query used to extract the data.
+     */
+    selectQuery?: string | null;
+  }
   /**
    * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \}
    */
@@ -604,19 +633,49 @@ export namespace alloydb_v1alpha {
      */
     kmsKeyVersions?: string[] | null;
   }
+  /**
+   * Export cluster request.
+   */
+  export interface Schema$ExportClusterRequest {
+    /**
+     * Options for exporting data in CSV format. Required field to be set for CSV file type.
+     */
+    csvExportOptions?: Schema$CsvExportOptions;
+    /**
+     * Required. Name of the database where the export command will be executed. Note - Value provided should be the same as expected from `SELECT current_database();` and NOT as a resource reference.
+     */
+    database?: string | null;
+    /**
+     * Required. Option to export data to cloud storage.
+     */
+    gcsDestination?: Schema$GcsDestination;
+    /**
+     * Options for exporting data in SQL format. Required field to be set for SQL file type.
+     */
+    sqlExportOptions?: Schema$SqlExportOptions;
+  }
   /**
    * Message for triggering failover on an Instance
    */
   export interface Schema$FailoverInstanceRequest {
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string | null;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the failover.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean | null;
   }
+  /**
+   * Destination for Export. Export will be done to cloud storage.
+   */
+  export interface Schema$GcsDestination {
+    /**
+     * Required. The path to the file in Google Cloud Storage where the export will be stored. The URI is in the form `gs://bucketName/fileName`.
+     */
+    uri?: string | null;
+  }
   /**
    * Cluster level configuration parameters related to the Gemini in Databases add-on.
    */
@@ -678,19 +737,19 @@ export namespace alloydb_v1alpha {
    */
   export interface Schema$GoogleTypeTimeOfDay {
     /**
-     * Hours of day in 24 hour format. Should be from 0 to 23. An API may choose to allow the value "24:00:00" for scenarios like business closing time.
+     * Hours of a day in 24 hour format. Must be greater than or equal to 0 and typically must be less than or equal to 23. An API may choose to allow the value "24:00:00" for scenarios like business closing time.
      */
     hours?: number | null;
     /**
-     * Minutes of hour of day. Must be from 0 to 59.
+     * Minutes of an hour. Must be greater than or equal to 0 and less than or equal to 59.
      */
     minutes?: number | null;
     /**
-     * Fractions of seconds in nanoseconds. Must be from 0 to 999,999,999.
+     * Fractions of seconds, in nanoseconds. Must be greater than or equal to 0 and less than or equal to 999,999,999.
      */
     nanos?: number | null;
     /**
-     * Seconds of minutes of the time. Must normally be from 0 to 59. An API may allow the value 60 if it allows leap-seconds.
+     * Seconds of a minute. Must be greater than or equal to 0 and typically must be less than or equal to 59. An API may allow the value 60 if it allows leap-seconds.
      */
     seconds?: number | null;
   }
@@ -703,11 +762,11 @@ export namespace alloydb_v1alpha {
      */
     faultType?: string | null;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string | null;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the fault injection.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean | null;
   }
@@ -732,7 +791,7 @@ export namespace alloydb_v1alpha {
      */
     createTime?: string | null;
     /**
-     * Database flags. Set at instance level. * They are copied from primary instance on read instance creation. * Read instances can set new or override existing flags that are relevant for reads, e.g. for enabling columnar cache on a read instance. Flags set on read instance may or may not be present on primary. This is a list of "key": "value" pairs. "key": The name of the flag. These flags are passed at instance setup time, so include both server options and system variables for Postgres. Flags are specified with underscores, not hyphens. "value": The value of the flag. Booleans are set to **on** for true and **off** for false. This field must be omitted if the flag doesn't take a value.
+     * Database flags. Set at the instance level. They are copied from the primary instance on secondary instance creation. Flags that have restrictions default to the value at primary instance on read instances during creation. Read instances can set new flags or override existing flags that are relevant for reads, for example, for enabling columnar cache on a read instance. Flags set on read instance might or might not be present on the primary instance. This is a list of "key": "value" pairs. "key": The name of the flag. These flags are passed at instance setup time, so include both server options and system variables for Postgres. Flags are specified with underscores, not hyphens. "value": The value of the flag. Booleans are set to **on** for true and **off** for false. This field must be omitted if the flag doesn't take a value.
      */
     databaseFlags?: {[key: string]: string} | null;
     /**
@@ -776,7 +835,7 @@ export namespace alloydb_v1alpha {
      */
     name?: string | null;
     /**
-     * Optional. Instance level network configuration.
+     * Optional. Instance-level network configuration.
      */
     networkConfig?: Schema$InstanceNetworkConfig;
     /**
@@ -841,7 +900,7 @@ export namespace alloydb_v1alpha {
     writableNode?: Schema$Node;
   }
   /**
-   * Metadata related to instance level network configuration.
+   * Metadata related to instance-level network configuration.
    */
   export interface Schema$InstanceNetworkConfig {
     /**
@@ -1056,19 +1115,19 @@ export namespace alloydb_v1alpha {
    */
   export interface Schema$Node {
     /**
-     * The identifier of the VM e.g. "test-read-0601-407e52be-ms3l".
+     * Output only. The identifier of the VM e.g. "test-read-0601-407e52be-ms3l".
      */
     id?: string | null;
     /**
-     * The private IP address of the VM e.g. "10.57.0.34".
+     * Output only. The private IP address of the VM e.g. "10.57.0.34".
      */
     ip?: string | null;
     /**
-     * Determined by state of the compute VM and postgres-service health. Compute VM state can have values listed in https://cloud.google.com/compute/docs/instances/instance-life-cycle and postgres-service health can have values: HEALTHY and UNHEALTHY.
+     * Output only. Determined by state of the compute VM and postgres-service health. Compute VM state can have values listed in https://cloud.google.com/compute/docs/instances/instance-life-cycle and postgres-service health can have values: HEALTHY and UNHEALTHY.
      */
     state?: string | null;
     /**
-     * The Compute Engine zone of the VM e.g. "us-central1-b".
+     * Output only. The Compute Engine zone of the VM e.g. "us-central1-b".
      */
     zoneId?: string | null;
   }
@@ -1155,7 +1214,7 @@ export namespace alloydb_v1alpha {
      */
     endTime?: string | null;
     /**
-     * Output only. Identifies whether the user has requested cancellation of the operation. Operations that have successfully been cancelled have Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.
+     * Output only. Identifies whether the user has requested cancellation of the operation. Operations that have successfully been cancelled have google.longrunning.Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.
      */
     requestedCancellation?: boolean | null;
     /**
@@ -1189,11 +1248,11 @@ export namespace alloydb_v1alpha {
      */
     etag?: string | null;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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 original operation with the same request ID was received, and if so, will ignore 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).
      */
     requestId?: string | null;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the delete.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean | null;
   }
@@ -1205,6 +1264,10 @@ export namespace alloydb_v1alpha {
      * Optional. Create an instance that allows connections from Private Service Connect endpoints to the instance.
      */
     pscEnabled?: boolean | null;
+    /**
+     * Output only. The project number that needs to be allowlisted on the network attachment to enable outbound connectivity.
+     */
+    serviceOwnedProjectNumber?: string | null;
   }
   /**
    * PscInstanceConfig contains PSC related configuration at an instance level.
@@ -1218,11 +1281,24 @@ export namespace alloydb_v1alpha {
      * Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
      */
     pscDnsName?: string | null;
+    /**
+     * Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. Currently we only support 0 or 1 PSC interface.
+     */
+    pscInterfaceConfigs?: Schema$PscInterfaceConfig[];
     /**
      * Output only. The service attachment created when Private Service Connect (PSC) is enabled for the instance. The name of the resource will be in the format of `projects//regions//serviceAttachments/`
      */
     serviceAttachmentLink?: string | null;
   }
+  /**
+   * Configuration for setting up a PSC interface to enable outbound connectivity.
+   */
+  export interface Schema$PscInterfaceConfig {
+    /**
+     * The network attachment resource created in the consumer network to which the PSC interface will be linked. This is of the format: "projects/${CONSUMER_PROJECT\}/regions/${REGION\}/networkAttachments/${NETWORK_ATTACHMENT_NAME\}". The network attachment must be in the same region as the instance.
+     */
+    networkAttachmentResource?: string | null;
+  }
   /**
    * A backup's position in a quantity-based retention queue, of backups with the same source cluster and type, with length, retention, specified by the backup's retention policy. Once the position is greater than the retention, the backup is eligible to be garbage collected. Example: 5 backups from the same source cluster and type with a quantity-based retention of 3 and denoted by backup_id (position, retention). Safe: backup_5 (1, 3), backup_4, (2, 3), backup_3 (3, 3). Awaiting garbage collection: backup_2 (4, 3), backup_1 (5, 3)
    */
@@ -1277,15 +1353,15 @@ export namespace alloydb_v1alpha {
   }
   export interface Schema$RestartInstanceRequest {
     /**
-     * Optional. Full name of the nodes as obtained from INSTANCE_VIEW_FULL to restart upon. Only applicable for read instances.
+     * Optional. Full name of the nodes as obtained from INSTANCE_VIEW_FULL to restart upon. Applicable only to read instances.
      */
     nodeIds?: string[] | null;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string | null;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the restart.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean | null;
   }
@@ -1310,14 +1386,31 @@ export namespace alloydb_v1alpha {
      */
     continuousBackupSource?: Schema$ContinuousBackupSource;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string | null;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the import request.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean | null;
   }
+  /**
+   * Message for registering Restoring from CloudSQL resource.
+   */
+  export interface Schema$RestoreFromCloudSQLRequest {
+    /**
+     * Cluster created from CloudSQL backup run.
+     */
+    cloudsqlBackupRunSource?: Schema$CloudSQLBackupRunSource;
+    /**
+     * Required. The resource being created
+     */
+    cluster?: Schema$Cluster;
+    /**
+     * Required. ID of the requesting object.
+     */
+    clusterId?: string | null;
+  }
   /**
    * Configuration information for the secondary cluster. This should be set if and only if the cluster is of type SECONDARY.
    */
@@ -1327,6 +1420,27 @@ export namespace alloydb_v1alpha {
      */
     primaryClusterName?: string | null;
   }
+  /**
+   * Options for exporting data in SQL format.
+   */
+  export interface Schema$SqlExportOptions {
+    /**
+     * Optional. If true, output commands to DROP all the dumped database objects prior to outputting the commands for creating them.
+     */
+    cleanTargetObjects?: boolean | null;
+    /**
+     * Optional. If true, use DROP ... IF EXISTS commands to check for the object's existence before dropping it in clean_target_objects mode.
+     */
+    ifExistTargetObjects?: boolean | null;
+    /**
+     * Optional. If true, only export the schema.
+     */
+    schemaOnly?: boolean | null;
+    /**
+     * Optional. Tables to export from.
+     */
+    tables?: string[] | null;
+  }
   /**
    * SSL configuration.
    */
@@ -1554,7 +1668,7 @@ export namespace alloydb_v1alpha {
     uniqueId?: string | null;
   }
   /**
-   * Common model for database resource instance metadata.
+   * Common model for database resource instance metadata. Next ID: 23
    */
   export interface Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceMetadata {
     /**
@@ -1581,6 +1695,10 @@ export namespace alloydb_v1alpha {
      * Any custom metadata associated with the resource
      */
     customMetadata?: Schema$StorageDatabasecenterPartnerapiV1mainCustomMetadataData;
+    /**
+     * Optional. Edition represents whether the instance is ENTERPRISE or ENTERPRISE_PLUS. This information is core to Cloud SQL only and is used to identify the edition of the instance.
+     */
+    edition?: string | null;
     /**
      * Entitlements associated with the resource
      */
@@ -1609,6 +1727,10 @@ export namespace alloydb_v1alpha {
      * Identifier for this resource's immediate parent/primary resource if the current resource is a replica or derived form of another Database resource. Else it would be NULL. REQUIRED if the immediate parent exists when first time resource is getting ingested, otherwise optional.
      */
     primaryResourceId?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceId;
+    /**
+     * Primary resource location. REQUIRED if the immediate parent exists when first time resource is getting ingested, otherwise optional.
+     */
+    primaryResourceLocation?: string | null;
     /**
      * The product this resource represents.
      */
@@ -1621,6 +1743,10 @@ export namespace alloydb_v1alpha {
      * Required. Different from DatabaseResourceId.unique_id, a resource name can be reused over time. That is, after a resource named "ABC" is deleted, the name "ABC" can be used to to create a new resource within the same source. Resource name to follow CAIS resource_name format as noted here go/condor-common-datamodel
      */
     resourceName?: string | null;
+    /**
+     * Optional. Tags associated with this resources.
+     */
+    tagsSet?: Schema$StorageDatabasecenterPartnerapiV1mainTags;
     /**
      * The time at which the resource was updated and recorded at partner service.
      */
@@ -1704,13 +1830,21 @@ export namespace alloydb_v1alpha {
    */
   export interface Schema$StorageDatabasecenterPartnerapiV1mainMachineConfiguration {
     /**
-     * The number of CPUs. TODO(b/342344482, b/342346271) add proto validations again after bug fix.
+     * The number of CPUs. Deprecated. Use vcpu_count instead. TODO(b/342344482, b/342346271) add proto validations again after bug fix.
      */
     cpuCount?: number | null;
     /**
      * Memory size in bytes. TODO(b/342344482, b/342346271) add proto validations again after bug fix.
      */
     memorySizeInBytes?: string | null;
+    /**
+     * Optional. Number of shards (if applicable).
+     */
+    shardCount?: number | null;
+    /**
+     * Optional. The number of vCPUs. TODO(b/342344482, b/342346271) add proto validations again after bug fix.
+     */
+    vcpuCount?: number | null;
   }
   export interface Schema$StorageDatabasecenterPartnerapiV1mainObservabilityMetricData {
     /**
@@ -1749,12 +1883,29 @@ export namespace alloydb_v1alpha {
     message?: string | null;
   }
   export interface Schema$StorageDatabasecenterPartnerapiV1mainRetentionSettings {
+    /**
+     * Duration based retention period i.e. 172800 seconds (2 days)
+     */
+    durationBasedRetention?: string | null;
     quantityBasedRetention?: number | null;
     /**
      * The unit that 'retained_backups' represents.
      */
     retentionUnit?: string | null;
     timeBasedRetention?: string | null;
+    /**
+     * Timestamp based retention period i.e. 2024-05-01T00:00:00Z
+     */
+    timestampBasedRetentionTime?: string | null;
+  }
+  /**
+   * Message type for storing tags. Tags provide a way to create annotations for resources, and in some cases conditionally allow or deny policies based on whether a resource has a specific tag.
+   */
+  export interface Schema$StorageDatabasecenterPartnerapiV1mainTags {
+    /**
+     * The Tag key/value mappings.
+     */
+    tags?: {[key: string]: string} | null;
   }
   /**
    * Message type for storing user labels. User labels are used to tag App Engine resources, allowing users to search for resources matching a set of labels and to aggregate usage data by labels.
@@ -1848,11 +1999,11 @@ export namespace alloydb_v1alpha {
    */
   export interface Schema$SwitchoverClusterRequest {
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string | null;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the delete.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean | null;
   }
@@ -1904,11 +2055,11 @@ export namespace alloydb_v1alpha {
      */
     etag?: string | null;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string | null;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but does not actually execute the upgrade.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean | null;
     /**
@@ -2680,7 +2831,7 @@ export namespace alloydb_v1alpha {
      */
     parent?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
@@ -2704,7 +2855,7 @@ export namespace alloydb_v1alpha {
      */
     name?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
@@ -2753,7 +2904,7 @@ export namespace alloydb_v1alpha {
      */
     name?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
@@ -3044,6 +3195,94 @@ export namespace alloydb_v1alpha {
       }
     }
 
+    /**
+     * Exports data from the cluster. Imperative only.
+     *
+     * @param params - Parameters for request
+     * @param options - Optionally override request options, such as `url`, `method`, and `encoding`.
+     * @param callback - Optional callback that handles the response.
+     * @returns A promise if used with async/await, or void if used with a callback.
+     */
+    export(
+      params: Params$Resource$Projects$Locations$Clusters$Export,
+      options: StreamMethodOptions
+    ): GaxiosPromise<Readable>;
+    export(
+      params?: Params$Resource$Projects$Locations$Clusters$Export,
+      options?: MethodOptions
+    ): GaxiosPromise<Schema$Operation>;
+    export(
+      params: Params$Resource$Projects$Locations$Clusters$Export,
+      options: StreamMethodOptions | BodyResponseCallback<Readable>,
+      callback: BodyResponseCallback<Readable>
+    ): void;
+    export(
+      params: Params$Resource$Projects$Locations$Clusters$Export,
+      options: MethodOptions | BodyResponseCallback<Schema$Operation>,
+      callback: BodyResponseCallback<Schema$Operation>
+    ): void;
+    export(
+      params: Params$Resource$Projects$Locations$Clusters$Export,
+      callback: BodyResponseCallback<Schema$Operation>
+    ): void;
+    export(callback: BodyResponseCallback<Schema$Operation>): void;
+    export(
+      paramsOrCallback?:
+        | Params$Resource$Projects$Locations$Clusters$Export
+        | BodyResponseCallback<Schema$Operation>
+        | BodyResponseCallback<Readable>,
+      optionsOrCallback?:
+        | MethodOptions
+        | StreamMethodOptions
+        | BodyResponseCallback<Schema$Operation>
+        | BodyResponseCallback<Readable>,
+      callback?:
+        | BodyResponseCallback<Schema$Operation>
+        | BodyResponseCallback<Readable>
+    ): void | GaxiosPromise<Schema$Operation> | GaxiosPromise<Readable> {
+      let params = (paramsOrCallback ||
+        {}) as Params$Resource$Projects$Locations$Clusters$Export;
+      let options = (optionsOrCallback || {}) as MethodOptions;
+
+      if (typeof paramsOrCallback === 'function') {
+        callback = paramsOrCallback;
+        params = {} as Params$Resource$Projects$Locations$Clusters$Export;
+        options = {};
+      }
+
+      if (typeof optionsOrCallback === 'function') {
+        callback = optionsOrCallback;
+        options = {};
+      }
+
+      const rootUrl = options.rootUrl || 'https://alloydb.googleapis.com/';
+      const parameters = {
+        options: Object.assign(
+          {
+            url: (rootUrl + '/v1alpha/{+name}:export').replace(
+              /([^:]\/)\/+/g,
+              '$1'
+            ),
+            method: 'POST',
+            apiVersion: '',
+          },
+          options
+        ),
+        params,
+        requiredParams: ['name'],
+        pathParams: ['name'],
+        context: this.context,
+      };
+      if (callback) {
+        createAPIRequest<Schema$Operation>(
+          parameters,
+          callback as BodyResponseCallback<unknown>
+        );
+      } else {
+        return createAPIRequest<Schema$Operation>(parameters);
+      }
+    }
+
     /**
      * Gets details of a single Cluster.
      *
@@ -3484,7 +3723,95 @@ export namespace alloydb_v1alpha {
     }
 
     /**
-     * Switches the role of PRIMARY and SECONDARY cluster without any data loss. This promotes the SECONDARY cluster to PRIMARY and sets up original PRIMARY cluster to replicate from this newly promoted cluster.
+     * Restores an AlloyDB cluster from a CloudSQL resource.
+     *
+     * @param params - Parameters for request
+     * @param options - Optionally override request options, such as `url`, `method`, and `encoding`.
+     * @param callback - Optional callback that handles the response.
+     * @returns A promise if used with async/await, or void if used with a callback.
+     */
+    restoreFromCloudSQL(
+      params: Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql,
+      options: StreamMethodOptions
+    ): GaxiosPromise<Readable>;
+    restoreFromCloudSQL(
+      params?: Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql,
+      options?: MethodOptions
+    ): GaxiosPromise<Schema$Operation>;
+    restoreFromCloudSQL(
+      params: Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql,
+      options: StreamMethodOptions | BodyResponseCallback<Readable>,
+      callback: BodyResponseCallback<Readable>
+    ): void;
+    restoreFromCloudSQL(
+      params: Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql,
+      options: MethodOptions | BodyResponseCallback<Schema$Operation>,
+      callback: BodyResponseCallback<Schema$Operation>
+    ): void;
+    restoreFromCloudSQL(
+      params: Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql,
+      callback: BodyResponseCallback<Schema$Operation>
+    ): void;
+    restoreFromCloudSQL(callback: BodyResponseCallback<Schema$Operation>): void;
+    restoreFromCloudSQL(
+      paramsOrCallback?:
+        | Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql
+        | BodyResponseCallback<Schema$Operation>
+        | BodyResponseCallback<Readable>,
+      optionsOrCallback?:
+        | MethodOptions
+        | StreamMethodOptions
+        | BodyResponseCallback<Schema$Operation>
+        | BodyResponseCallback<Readable>,
+      callback?:
+        | BodyResponseCallback<Schema$Operation>
+        | BodyResponseCallback<Readable>
+    ): void | GaxiosPromise<Schema$Operation> | GaxiosPromise<Readable> {
+      let params = (paramsOrCallback ||
+        {}) as Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql;
+      let options = (optionsOrCallback || {}) as MethodOptions;
+
+      if (typeof paramsOrCallback === 'function') {
+        callback = paramsOrCallback;
+        params =
+          {} as Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql;
+        options = {};
+      }
+
+      if (typeof optionsOrCallback === 'function') {
+        callback = optionsOrCallback;
+        options = {};
+      }
+
+      const rootUrl = options.rootUrl || 'https://alloydb.googleapis.com/';
+      const parameters = {
+        options: Object.assign(
+          {
+            url: (
+              rootUrl + '/v1alpha/{+parent}/clusters:restoreFromCloudSQL'
+            ).replace(/([^:]\/)\/+/g, '$1'),
+            method: 'POST',
+            apiVersion: '',
+          },
+          options
+        ),
+        params,
+        requiredParams: ['parent'],
+        pathParams: ['parent'],
+        context: this.context,
+      };
+      if (callback) {
+        createAPIRequest<Schema$Operation>(
+          parameters,
+          callback as BodyResponseCallback<unknown>
+        );
+      } else {
+        return createAPIRequest<Schema$Operation>(parameters);
+      }
+    }
+
+    /**
+     * Switches the roles of PRIMARY and SECONDARY clusters without any data loss. This promotes the SECONDARY cluster to PRIMARY and sets up the original PRIMARY cluster to replicate from this newly promoted cluster.
      *
      * @param params - Parameters for request
      * @param options - Optionally override request options, such as `url`, `method`, and `encoding`.
@@ -3671,11 +3998,11 @@ export namespace alloydb_v1alpha {
      */
     parent?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the create request.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean;
 
@@ -3695,11 +4022,11 @@ export namespace alloydb_v1alpha {
      */
     parent?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the create request.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean;
 
@@ -3723,14 +4050,26 @@ export namespace alloydb_v1alpha {
      */
     name?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the delete.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean;
   }
+  export interface Params$Resource$Projects$Locations$Clusters$Export
+    extends StandardParameters {
+    /**
+     * Required. The resource name of the cluster.
+     */
+    name?: string;
+
+    /**
+     * Request body metadata
+     */
+    requestBody?: Schema$ExportClusterRequest;
+  }
   export interface Params$Resource$Projects$Locations$Clusters$Get
     extends StandardParameters {
     /**
@@ -3776,7 +4115,7 @@ export namespace alloydb_v1alpha {
      */
     name?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
@@ -3784,7 +4123,7 @@ export namespace alloydb_v1alpha {
      */
     updateMask?: string;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the update request.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean;
 
@@ -3817,6 +4156,18 @@ export namespace alloydb_v1alpha {
      */
     requestBody?: Schema$RestoreClusterRequest;
   }
+  export interface Params$Resource$Projects$Locations$Clusters$Restorefromcloudsql
+    extends StandardParameters {
+    /**
+     * Required. The location of the new cluster. For the required format, see the comment on Cluster.name field.
+     */
+    parent?: string;
+
+    /**
+     * Request body metadata
+     */
+    requestBody?: Schema$RestoreFromCloudSQLRequest;
+  }
   export interface Params$Resource$Projects$Locations$Clusters$Switchover
     extends StandardParameters {
     /**
@@ -4747,11 +5098,11 @@ export namespace alloydb_v1alpha {
      */
     parent?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the create request.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean;
 
@@ -4771,11 +5122,11 @@ export namespace alloydb_v1alpha {
      */
     parent?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the create request.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean;
 
@@ -4795,11 +5146,11 @@ export namespace alloydb_v1alpha {
      */
     name?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the delete.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean;
   }
@@ -4833,7 +5184,7 @@ export namespace alloydb_v1alpha {
      */
     parent?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
   }
@@ -4883,7 +5234,7 @@ export namespace alloydb_v1alpha {
      */
     name?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
@@ -4891,7 +5242,7 @@ export namespace alloydb_v1alpha {
      */
     updateMask?: string;
     /**
-     * Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the update request.
+     * Optional. If set, performs request validation, for example, permission checks and any other type of validation, but does not actually execute the create request.
      */
     validateOnly?: boolean;
 
@@ -5361,7 +5712,7 @@ export namespace alloydb_v1alpha {
      */
     parent?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
@@ -5385,7 +5736,7 @@ export namespace alloydb_v1alpha {
      */
     name?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
@@ -5434,7 +5785,7 @@ export namespace alloydb_v1alpha {
      */
     name?: string;
     /**
-     * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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 original operation with the same request ID was received, and if so, will ignore 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).
+     * 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).
      */
     requestId?: string;
     /**
@@ -5459,7 +5810,7 @@ export namespace alloydb_v1alpha {
     }
 
     /**
-     * Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.
+     * Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.
      *
      * @param params - Parameters for request
      * @param options - Optionally override request options, such as `url`, `method`, and `encoding`.