@googleapis/alloydb 11.1.0 → 12.1.0

package/build/v1beta.d.ts

@@ -93,7 +93,7 @@ export declare namespace alloydb_v1beta {
          */
         enabled?: boolean | null;
         /**
-         * Optional. The encryption config can be specified to encrypt the backups with a customer-managed encryption key (CMEK). When this field is not specified, the backup will then use default encryption scheme to protect the user data.
+         * Optional. The encryption config can be specified to encrypt the backups with a customer-managed encryption key (CMEK). When this field is not specified, the backup will use the cluster's encryption config.
          */
         encryptionConfig?: Schema$EncryptionConfig;
         /**
@@ -137,6 +137,10 @@ export declare namespace alloydb_v1beta {
          * Output only. The system-generated UID of the cluster which was used to create this resource.
          */
         clusterUid?: string | null;
+        /**
+         * Output only. Timestamp when the resource finished being created.
+         */
+        createCompletionTime?: string | null;
         /**
          * Output only. Create time stamp
          */
@@ -203,6 +207,12 @@ export declare namespace alloydb_v1beta {
          * 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.
          */
@@ -212,7 +222,7 @@ export declare namespace alloydb_v1beta {
          */
         uid?: string | null;
         /**
-         * Output only. Update time stamp
+         * Output only. Update time stamp Users should not infer any meaning from this field. Its value is generally unrelated to the timing of the backup creation operation.
          */
         updateTime?: string | null;
     }
@@ -238,7 +248,7 @@ export declare namespace alloydb_v1beta {
          */
         requireConnectors?: boolean | null;
         /**
-         * Optional. SSL config option for this instance.
+         * Optional. SSL configuration option for this instance.
          */
         sslConfig?: Schema$SslConfig;
     }
@@ -335,7 +345,7 @@ export declare namespace alloydb_v1beta {
          */
         etag?: string | null;
         /**
-         * Optional. Configuration parameters related to the Gemini in Databases add-on.
+         * Optional. Deprecated and unused. This field will be removed in the near future.
          */
         geminiConfig?: Schema$GeminiClusterConfig;
         /**
@@ -401,6 +411,12 @@ export declare namespace alloydb_v1beta {
          * 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
          */
@@ -472,6 +488,61 @@ export declare namespace alloydb_v1beta {
          */
         publicIpAddress?: string | null;
     }
+    /**
+     * Configuration for Managed Connection Pool (MCP).
+     */
+    export interface Schema$ConnectionPoolConfig {
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The default pool size. Defaults to 20.
+         */
+        defaultPoolSize?: string | null;
+        /**
+         * Optional. Deprecated; Prefer 'enabled' as this will be removed soon.
+         */
+        enable?: boolean | null;
+        /**
+         * Optional. Whether to enable Managed Connection Pool (MCP).
+         */
+        enabled?: boolean | null;
+        /**
+         * Optional. Connection Pool flags, as a list of "key": "value" pairs.
+         */
+        flags?: {
+            [key: string]: string;
+        } | null;
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The list of startup parameters to ignore. Defaults to ["extra_float_digits"]
+         */
+        ignoreStartupParameters?: string[] | null;
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The maximum number of client connections allowed.
+         */
+        maxClientConn?: string | null;
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The maximum number of prepared statements allowed. MCP makes sure that any statement prepared by a client, up to this limit, is available on the backing server connection in transaction and statement pooling mode. Even if the statement was originally prepared on another server connection. Defaults to 0.
+         */
+        maxPreparedStatements?: string | null;
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The minimum pool size. Defaults to 0.
+         */
+        minPoolSize?: string | null;
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The pool mode. Defaults to `POOL_MODE_TRANSACTION`.
+         */
+        poolMode?: string | null;
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The maximum number of seconds queries are allowed to spend waiting for execution. If the query is not assigned to a server during that time, the client is disconnected. 0 disables.
+         */
+        queryWaitTimeout?: string | null;
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The maximum number of seconds a server is allowed to be idle before it is disconnected. 0 disables.
+         */
+        serverIdleTimeout?: string | null;
+        /**
+         * Optional. Deprecated. Use 'flags' instead. The list of users that are allowed to connect to the MCP stats console. The users must exist in the database.
+         */
+        statsUsers?: string[] | null;
+    }
     /**
      * ContinuousBackupConfig describes the continuous backups recovery configurations of a cluster.
      */
@@ -481,7 +552,7 @@ export declare namespace alloydb_v1beta {
          */
         enabled?: boolean | null;
         /**
-         * The encryption config can be specified to encrypt the backups with a customer-managed encryption key (CMEK). When this field is not specified, the backup will then use default encryption scheme to protect the user data.
+         * The encryption config can be specified to encrypt the backups with a customer-managed encryption key (CMEK). When this field is not specified, the backup will use the cluster's encryption config.
          */
         encryptionConfig?: Schema$EncryptionConfig;
         /**
@@ -523,6 +594,69 @@ export declare namespace alloydb_v1beta {
          */
         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;
+    }
+    /**
+     * Options for importing data in CSV format.
+     */
+    export interface Schema$CsvImportOptions {
+        /**
+         * Optional. The columns to which CSV data is imported. If not specified, all columns of the database table are loaded with CSV data.
+         */
+        columns?: string[] | null;
+        /**
+         * Optional. Specifies the character that should appear before a data character that needs to be escaped. The default is 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 database table to import CSV file into.
+         */
+        table?: string | null;
+    }
+    /**
+     * DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date.
+     */
+    export interface Schema$DenyMaintenancePeriod {
+        /**
+         * Deny period end date. This can be: * A full date, with non-zero year, month and day values OR * A month and day value, with a zero year for recurring
+         */
+        endDate?: Schema$GoogleTypeDate;
+        /**
+         * Deny period start date. This can be: * A full date, with non-zero year, month and day values OR * A month and day value, with a zero year for recurring
+         */
+        startDate?: Schema$GoogleTypeDate;
+        /**
+         * Time in UTC when the deny period starts on start_date and ends on end_date. This can be: * Full time OR * All zeros for 00:00:00 UTC
+         */
+        time?: Schema$GoogleTypeTimeOfDay;
+    }
     /**
      * 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); \}
      */
@@ -550,34 +684,73 @@ export declare namespace alloydb_v1beta {
          */
         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;
     }
     /**
-     * Cluster level configuration parameters related to the Gemini in Databases add-on.
+     * Instance level configuration parameters related to the Gemini Cloud Assist product.
+     */
+    export interface Schema$GCAInstanceConfig {
+        /**
+         * Output only. Represents the GCA entitlement state of the instance.
+         */
+        gcaEntitlement?: string | 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;
+    }
+    /**
+     * Deprecated and unused. This field will be removed in the near future.
      */
     export interface Schema$GeminiClusterConfig {
         /**
-         * Output only. Whether the Gemini in Databases add-on is enabled for the cluster. It will be true only if the add-on has been enabled for the billing account corresponding to the cluster. Its status is toggled from the Admin Control Center (ACC) and cannot be toggled using AlloyDB's APIs.
+         * Output only. Deprecated and unused. This field will be removed in the near future.
          */
         entitled?: boolean | null;
     }
     /**
-     * Instance level configuration parameters related to the Gemini in Databases add-on.
+     * Deprecated and unused. This field will be removed in the near future.
      */
     export interface Schema$GeminiInstanceConfig {
         /**
-         * Output only. Whether the Gemini in Databases add-on is enabled for the instance. It will be true only if the add-on has been enabled for the billing account corresponding to the instance. Its status is toggled from the Admin Control Center (ACC) and cannot be toggled using AlloyDB's APIs.
+         * Output only. Deprecated and unused. This field will be removed in the near future.
          */
         entitled?: boolean | null;
     }
@@ -623,27 +796,69 @@ export declare namespace alloydb_v1beta {
          */
         name?: string | null;
     }
+    /**
+     * Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp
+     */
+    export interface Schema$GoogleTypeDate {
+        /**
+         * Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
+         */
+        day?: number | null;
+        /**
+         * Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
+         */
+        month?: number | null;
+        /**
+         * Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
+         */
+        year?: number | null;
+    }
     /**
      * Represents a time of day. The date and time zone are either not significant or are specified elsewhere. An API may choose to allow leap seconds. Related types are google.type.Date and `google.protobuf.Timestamp`.
      */
     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;
     }
+    /**
+     * Import cluster request.
+     */
+    export interface Schema$ImportClusterRequest {
+        /**
+         * Options for importing data in CSV format.
+         */
+        csvImportOptions?: Schema$CsvImportOptions;
+        /**
+         * Optional. Name of the database to which the import will be done. For import from SQL file, this is required only if the file does not specify a database. Note - Value provided should be the same as expected from `SELECT current_database();` and NOT as a resource reference.
+         */
+        database?: string | null;
+        /**
+         * Required. The path to the file in Google Cloud Storage where the source file for import will be stored. The URI is in the form `gs://bucketName/fileName`.
+         */
+        gcsUri?: string | null;
+        /**
+         * Options for importing data in SQL format.
+         */
+        sqlImportOptions?: Schema$SqlImportOptions;
+        /**
+         * Optional. Database user to be used for importing the data. Note - Value provided should be the same as expected from `SELECT current_user;` and NOT as a resource reference.
+         */
+        user?: string | null;
+    }
     /**
      * Message for triggering fault injection on an instance
      */
@@ -653,11 +868,11 @@ export declare namespace alloydb_v1beta {
          */
         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;
     }
@@ -679,12 +894,16 @@ export declare namespace alloydb_v1beta {
          * Optional. Client connection specific configurations
          */
         clientConnectionConfig?: Schema$ClientConnectionConfig;
+        /**
+         * Optional. The configuration for Managed Connection Pool (MCP).
+         */
+        connectionPoolConfig?: Schema$ConnectionPoolConfig;
         /**
          * Output only. Create time stamp
          */
         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;
@@ -701,12 +920,16 @@ export declare namespace alloydb_v1beta {
          * For Resource freshness validation (https://google.aip.dev/154)
          */
         etag?: string | null;
+        /**
+         * Output only. Configuration parameters related to Gemini Cloud Assist.
+         */
+        gcaConfig?: Schema$GCAInstanceConfig;
         /**
          * The Compute Engine zone that the instance should serve from, per https://cloud.google.com/compute/docs/regions-zones This can ONLY be specified for ZONAL instances. If present for a REGIONAL instance, an error will be thrown. If this is absent for a ZONAL instance, instance is created in a random zone with available capacity.
          */
         gceZone?: string | null;
         /**
-         * Optional. Configuration parameters related to the Gemini in Databases add-on.
+         * Optional. Deprecated and unused. This field will be removed in the near future.
          */
         geminiConfig?: Schema$GeminiInstanceConfig;
         /**
@@ -732,7 +955,7 @@ export declare namespace alloydb_v1beta {
          */
         name?: string | null;
         /**
-         * Optional. Instance level network configuration.
+         * Optional. Instance-level network configuration.
          */
         networkConfig?: Schema$InstanceNetworkConfig;
         /**
@@ -793,7 +1016,7 @@ export declare namespace alloydb_v1beta {
         writableNode?: Schema$Node;
     }
     /**
-     * Metadata related to instance level network configuration.
+     * Metadata related to instance-level network configuration.
      */
     export interface Schema$InstanceNetworkConfig {
         /**
@@ -808,6 +1031,10 @@ export declare namespace alloydb_v1beta {
          * Optional. Enabling public ip for the instance.
          */
         enablePublicIp?: boolean | null;
+        /**
+         * Output only. The resource link for the VPC network in which instance resources are created and from which they are accessible via Private IP. This will be the same value as the parent cluster's network. It is specified in the form: // `projects/{project_number\}/global/networks/{network_id\}`.
+         */
+        network?: string | null;
     }
     /**
      * Details regarding the upgrade of instaces associated with a cluster.
@@ -941,6 +1168,10 @@ export declare namespace alloydb_v1beta {
          * The number of CPU's in the VM instance.
          */
         cpuCount?: number | null;
+        /**
+         * Machine type of the VM instance. E.g. "n2-highmem-4", "n2-highmem-8", "c4a-highmem-4-lssd". cpu_count must match the number of vCPUs in the machine type.
+         */
+        machineType?: string | null;
     }
     /**
      * MaintenanceSchedule stores the maintenance schedule generated from the MaintenanceUpdatePolicy, once a maintenance rollout is triggered, if MaintenanceWindow is set, and if there is no conflicting DenyPeriod. The schedule is cleared once the update takes place. This field cannot be manually changed; modify the MaintenanceUpdatePolicy instead.
@@ -955,6 +1186,10 @@ export declare namespace alloydb_v1beta {
      * MaintenanceUpdatePolicy defines the policy for system updates.
      */
     export interface Schema$MaintenanceUpdatePolicy {
+        /**
+         * Periods to deny maintenance. Currently limited to 1.
+         */
+        denyMaintenancePeriods?: Schema$DenyMaintenancePeriod[];
         /**
          * Preferred windows to perform maintenance. Currently limited to 1.
          */
@@ -1004,23 +1239,23 @@ export declare namespace alloydb_v1beta {
         network?: string | null;
     }
     /**
-     * Details of a single node in the instance. Nodes in an AlloyDB instance are ephemereal, they can change during update, failover, autohealing and resize operations.
+     * Details of a single node in the instance. Nodes in an AlloyDB instance are ephemeral, they can change during update, failover, autohealing and resize operations.
      */
     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;
     }
@@ -1028,6 +1263,10 @@ export declare namespace alloydb_v1beta {
      * Observability Instance specific configuration.
      */
     export interface Schema$ObservabilityInstanceConfig {
+        /**
+         * Whether assistive experiences are enabled for this AlloyDB instance.
+         */
+        assistiveExperiencesEnabled?: boolean | null;
         /**
          * Observability feature status for an instance. This flag is turned "off" by default.
          */
@@ -1052,16 +1291,12 @@ export declare namespace alloydb_v1beta {
          * Track actively running queries on the instance. If not set, this flag is "off" by default.
          */
         trackActiveQueries?: boolean | null;
-        /**
-         * Track client address for an instance. If not set, default value is "off".
-         */
-        trackClientAddress?: boolean | null;
         /**
          * Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on.
          */
         trackWaitEvents?: boolean | null;
         /**
-         * Output only. Track wait event types during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. This is read-only flag and only modifiable by producer API.
+         * Output only. Track wait event types during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. This is read-only flag and only modifiable by internal API.
          */
         trackWaitEventTypes?: boolean | null;
     }
@@ -1111,7 +1346,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -1122,6 +1357,10 @@ export declare namespace alloydb_v1beta {
          * Output only. Server-defined resource path for the target of the operation.
          */
         target?: string | null;
+        /**
+         * Output only. UpgradeClusterStatus related metadata.
+         */
+        upgradeClusterStatus?: Schema$UpgradeClusterStatus;
         /**
          * Output only. Name of the verb executed by the operation.
          */
@@ -1145,14 +1384,39 @@ export declare namespace alloydb_v1beta {
          */
         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;
     }
+    /**
+     * Configuration for setting up PSC service automation. Consumer projects in the configs will be allowlisted automatically for the instance.
+     */
+    export interface Schema$PscAutoConnectionConfig {
+        /**
+         * The consumer network for the PSC service automation, example: "projects/vpc-host-project/global/networks/default". The consumer network might be hosted a different project than the consumer project.
+         */
+        consumerNetwork?: string | null;
+        /**
+         * Output only. The status of the service connection policy. Possible values: "STATE_UNSPECIFIED" - Default state, when Connection Map is created initially. "VALID" - Set when policy and map configuration is valid, and their matching can lead to allowing creation of PSC Connections subject to other constraints like connections limit. "CONNECTION_POLICY_MISSING" - No Service Connection Policy found for this network and Service Class "POLICY_LIMIT_REACHED" - Service Connection Policy limit reached for this network and Service Class "CONSUMER_INSTANCE_PROJECT_NOT_ALLOWLISTED" - The consumer instance project is not in AllowedGoogleProducersResourceHierarchyLevels of the matching ServiceConnectionPolicy.
+         */
+        consumerNetworkStatus?: string | null;
+        /**
+         * The consumer project to which the PSC service automation endpoint will be created.
+         */
+        consumerProject?: string | null;
+        /**
+         * Output only. The IP address of the PSC service automation endpoint.
+         */
+        ipAddress?: string | null;
+        /**
+         * Output only. The status of the PSC service automation connection. Possible values: "STATE_UNSPECIFIED" - An invalid state as the default case. "ACTIVE" - The connection has been created successfully. "FAILED" - The connection is not functional since some resources on the connection fail to be created. "CREATING" - The connection is being created. "DELETING" - The connection is being deleted. "CREATE_REPAIRING" - The connection is being repaired to complete creation. "DELETE_REPAIRING" - The connection is being repaired to complete deletion.
+         */
+        status?: string | null;
+    }
     /**
      * PscConfig contains PSC related configuration at a cluster level.
      */
@@ -1161,6 +1425,10 @@ export declare namespace alloydb_v1beta {
          * 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.
@@ -1170,15 +1438,32 @@ export declare namespace alloydb_v1beta {
          * Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance.
          */
         allowedConsumerProjects?: string[] | null;
+        /**
+         * Optional. Configurations for setting up PSC service automation.
+         */
+        pscAutoConnections?: Schema$PscAutoConnectionConfig[];
         /**
          * 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)
      */
@@ -1231,22 +1516,31 @@ export declare namespace alloydb_v1beta {
          */
         nodeCount?: number | null;
     }
+    /**
+     * Read pool instances upgrade specific status.
+     */
+    export interface Schema$ReadPoolInstancesUpgradeStageStatus {
+        /**
+         * Read pool instances upgrade statistics.
+         */
+        upgradeStats?: Schema$Stats;
+    }
     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;
     }
     /**
-     * Message for restoring a Cluster from a backup or another cluster at a given point in time.
+     * Message for restoring a Cluster from a backup or another cluster at a given point in time. NEXT_ID: 11
      */
     export interface Schema$RestoreClusterRequest {
         /**
@@ -1266,14 +1560,31 @@ export declare namespace alloydb_v1beta {
          */
         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.
      */
@@ -1283,6 +1594,32 @@ export declare namespace alloydb_v1beta {
          */
         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;
+    }
+    /**
+     * Options for importing data in SQL format.
+     */
+    export interface Schema$SqlImportOptions {
+    }
     /**
      * SSL configuration.
      */
@@ -1313,6 +1650,44 @@ export declare namespace alloydb_v1beta {
          */
         status?: string | null;
     }
+    /**
+     * Status of an upgrade stage.
+     */
+    export interface Schema$StageStatus {
+        /**
+         * Read pool instances upgrade metadata.
+         */
+        readPoolInstancesUpgrade?: Schema$ReadPoolInstancesUpgradeStageStatus;
+        /**
+         * Upgrade stage.
+         */
+        stage?: string | null;
+        /**
+         * State of this stage.
+         */
+        state?: string | null;
+    }
+    /**
+     * Upgrade stats for read pool instances.
+     */
+    export interface Schema$Stats {
+        /**
+         * Number of read pool instances which failed to upgrade.
+         */
+        failed?: number | null;
+        /**
+         * Number of read pool instances for which upgrade has not started.
+         */
+        notStarted?: number | null;
+        /**
+         * Number of read pool instances undergoing upgrade.
+         */
+        ongoing?: number | null;
+        /**
+         * Number of read pool instances successfully upgraded.
+         */
+        success?: number | null;
+    }
     /**
      * The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).
      */
@@ -1336,6 +1711,10 @@ export declare namespace alloydb_v1beta {
      * Configuration for availability of database instance
      */
     export interface Schema$StorageDatabasecenterPartnerapiV1mainAvailabilityConfiguration {
+        /**
+         * Checks for existence of (multi-cluster) routing configuration that allows automatic failover to a different zone/region in case of an outage. Applicable to Bigtable resources.
+         */
+        automaticFailoverRoutingConfigured?: boolean | null;
         /**
          * Availability type. Potential values: * `ZONAL`: The instance serves data from only one zone. Outages in that zone affect data accessibility. * `REGIONAL`: The instance can serve data from more than one zone in a region (it is highly available).
          */
@@ -1510,7 +1889,7 @@ export declare namespace alloydb_v1beta {
         uniqueId?: string | null;
     }
     /**
-     * Common model for database resource instance metadata.
+     * Common model for database resource instance metadata. Next ID: 25
      */
     export interface Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceMetadata {
         /**
@@ -1537,6 +1916,10 @@ export declare namespace alloydb_v1beta {
          * 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
          */
@@ -1545,6 +1928,10 @@ export declare namespace alloydb_v1beta {
          * The state that the instance is expected to be in. For example, an instance state can transition to UNHEALTHY due to wrong patch update, while the expected state will remain at the HEALTHY.
          */
         expectedState?: string | null;
+        /**
+         * GCBDR configuration for the resource.
+         */
+        gcbdrConfiguration?: Schema$StorageDatabasecenterPartnerapiV1mainGCBDRConfiguration;
         /**
          * Required. Unique identifier for a Database resource
          */
@@ -1565,6 +1952,10 @@ export declare namespace alloydb_v1beta {
          * 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.
          */
@@ -1577,6 +1968,14 @@ export declare namespace alloydb_v1beta {
          * 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. Suspension reason for the resource.
+         */
+        suspensionReason?: string | null;
+        /**
+         * Optional. Tags associated with this resources.
+         */
+        tagsSet?: Schema$StorageDatabasecenterPartnerapiV1mainTags;
         /**
          * The time at which the resource was updated and recorded at partner service.
          */
@@ -1638,6 +2037,15 @@ export declare namespace alloydb_v1beta {
          */
         type?: string | null;
     }
+    /**
+     * GCBDR Configuration for the resource.
+     */
+    export interface Schema$StorageDatabasecenterPartnerapiV1mainGCBDRConfiguration {
+        /**
+         * Whether the resource is managed by GCBDR.
+         */
+        gcbdrManaged?: boolean | null;
+    }
     /**
      * Metadata for individual internal resources in an instance. e.g. spanner instance can have multiple databases with unique configuration settings. Similarly bigtable can have multiple clusters within same bigtable instance.
      */
@@ -1650,6 +2058,10 @@ export declare namespace alloydb_v1beta {
          * Information about the last backup attempt for this database
          */
         backupRun?: Schema$StorageDatabasecenterPartnerapiV1mainBackupRun;
+        /**
+         * Whether deletion protection is enabled for this internal resource.
+         */
+        isDeletionProtectionEnabled?: boolean | null;
         product?: Schema$StorageDatabasecenterProtoCommonProduct;
         resourceId?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceId;
         /**
@@ -1662,13 +2074,21 @@ export declare namespace alloydb_v1beta {
      */
     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) 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.
+         * Memory size in bytes. TODO(b/342344482) 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) add proto validations again after bug fix.
+         */
+        vcpuCount?: number | null;
     }
     export interface Schema$StorageDatabasecenterPartnerapiV1mainObservabilityMetricData {
         /**
@@ -1707,12 +2127,31 @@ export declare namespace alloydb_v1beta {
         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.
@@ -1789,10 +2228,22 @@ export declare namespace alloydb_v1beta {
          * The name of the flag resource, following Google Cloud conventions, e.g.: * projects/{project\}/locations/{location\}/flags/{flag\} This field currently has no semantic meaning.
          */
         name?: string | null;
+        /**
+         * The recommended value for an INTEGER flag.
+         */
+        recommendedIntegerValue?: string | null;
+        /**
+         * The recommended value for a STRING flag.
+         */
+        recommendedStringValue?: string | null;
         /**
          * Whether setting or updating this flag on an Instance requires a database restart. If a flag that requires database restart is set, the backend will automatically restart the database (making sure to satisfy any availability SLO's).
          */
         requiresDbRestart?: boolean | null;
+        /**
+         * The scope of the flag.
+         */
+        scope?: string | null;
         /**
          * Restriction on STRING type value.
          */
@@ -1808,11 +2259,11 @@ export declare namespace alloydb_v1beta {
      */
     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;
     }
@@ -1855,6 +2306,27 @@ export declare namespace alloydb_v1beta {
          */
         mode?: string | null;
     }
+    /**
+     * Upgrades a cluster.
+     */
+    export interface Schema$UpgradeClusterRequest {
+        /**
+         * Optional. The current etag of the Cluster. If an etag is provided and does not match the current etag of the Cluster, upgrade will be blocked and an ABORTED error will be returned.
+         */
+        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 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, for example, permission checks and any other type of validation, but does not actually execute the create request.
+         */
+        validateOnly?: boolean | null;
+        /**
+         * Required. The version the cluster is going to be upgraded to.
+         */
+        version?: string | null;
+    }
     /**
      * UpgradeClusterResponse contains the response for upgrade cluster operation.
      */
@@ -1872,6 +2344,31 @@ export declare namespace alloydb_v1beta {
          */
         status?: string | null;
     }
+    /**
+     * Message for current status of the Major Version Upgrade operation.
+     */
+    export interface Schema$UpgradeClusterStatus {
+        /**
+         * Whether the operation is cancellable.
+         */
+        cancellable?: boolean | null;
+        /**
+         * Source database major version.
+         */
+        sourceVersion?: string | null;
+        /**
+         * Status of all upgrade stages.
+         */
+        stages?: Schema$StageStatus[];
+        /**
+         * Cluster Major Version Upgrade state.
+         */
+        state?: string | null;
+        /**
+         * Target database major version.
+         */
+        targetVersion?: string | null;
+    }
     /**
      * Message describing User object.
      */
@@ -1880,6 +2377,10 @@ export declare namespace alloydb_v1beta {
          * Optional. List of database roles this user has. The database role strings are subject to the PostgreSQL naming conventions.
          */
         databaseRoles?: string[] | null;
+        /**
+         * Input only. If the user already exists and it has additional roles, keep them granted.
+         */
+        keepExtraRoles?: boolean | null;
         /**
          * Output only. Name of the resource in the form of projects/{project\}/locations/{location\}/cluster/{cluster\}/users/{user\}.
          */
@@ -1967,6 +2468,10 @@ export declare namespace alloydb_v1beta {
         name?: string;
     }
     export interface Params$Resource$Projects$Locations$List extends StandardParameters {
+        /**
+         * Optional. A list of extra location types that should be used as conditions for controlling the visibility of the locations.
+         */
+        extraLocationTypes?: string[];
         /**
          * A filter to narrow down results to a preferred subset. The filtering language accepts strings like `"displayName=tokyo"`, and is documented in more detail in [AIP-160](https://google.aip.dev/160).
          */
@@ -2068,7 +2573,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2090,7 +2595,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2136,7 +2641,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2199,6 +2704,20 @@ export declare namespace alloydb_v1beta {
         delete(params: Params$Resource$Projects$Locations$Clusters$Delete, options: MethodOptions | BodyResponseCallback<Schema$Operation>, callback: BodyResponseCallback<Schema$Operation>): void;
         delete(params: Params$Resource$Projects$Locations$Clusters$Delete, callback: BodyResponseCallback<Schema$Operation>): void;
         delete(callback: BodyResponseCallback<Schema$Operation>): void;
+        /**
+         * 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;
         /**
          * Gets details of a single Cluster.
          *
@@ -2213,6 +2732,20 @@ export declare namespace alloydb_v1beta {
         get(params: Params$Resource$Projects$Locations$Clusters$Get, options: MethodOptions | BodyResponseCallback<Schema$Cluster>, callback: BodyResponseCallback<Schema$Cluster>): void;
         get(params: Params$Resource$Projects$Locations$Clusters$Get, callback: BodyResponseCallback<Schema$Cluster>): void;
         get(callback: BodyResponseCallback<Schema$Cluster>): void;
+        /**
+         * Imports data to 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.
+         */
+        import(params: Params$Resource$Projects$Locations$Clusters$Import, options: StreamMethodOptions): GaxiosPromise<Readable>;
+        import(params?: Params$Resource$Projects$Locations$Clusters$Import, options?: MethodOptions): GaxiosPromise<Schema$Operation>;
+        import(params: Params$Resource$Projects$Locations$Clusters$Import, options: StreamMethodOptions | BodyResponseCallback<Readable>, callback: BodyResponseCallback<Readable>): void;
+        import(params: Params$Resource$Projects$Locations$Clusters$Import, options: MethodOptions | BodyResponseCallback<Schema$Operation>, callback: BodyResponseCallback<Schema$Operation>): void;
+        import(params: Params$Resource$Projects$Locations$Clusters$Import, callback: BodyResponseCallback<Schema$Operation>): void;
+        import(callback: BodyResponseCallback<Schema$Operation>): void;
         /**
          * Lists Clusters in a given project and location.
          *
@@ -2270,7 +2803,21 @@ export declare namespace alloydb_v1beta {
         restore(params: Params$Resource$Projects$Locations$Clusters$Restore, callback: BodyResponseCallback<Schema$Operation>): void;
         restore(callback: BodyResponseCallback<Schema$Operation>): void;
         /**
-         * 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;
+        /**
+         * 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`.
@@ -2283,6 +2830,20 @@ export declare namespace alloydb_v1beta {
         switchover(params: Params$Resource$Projects$Locations$Clusters$Switchover, options: MethodOptions | BodyResponseCallback<Schema$Operation>, callback: BodyResponseCallback<Schema$Operation>): void;
         switchover(params: Params$Resource$Projects$Locations$Clusters$Switchover, callback: BodyResponseCallback<Schema$Operation>): void;
         switchover(callback: BodyResponseCallback<Schema$Operation>): void;
+        /**
+         * Upgrades a single 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.
+         */
+        upgrade(params: Params$Resource$Projects$Locations$Clusters$Upgrade, options: StreamMethodOptions): GaxiosPromise<Readable>;
+        upgrade(params?: Params$Resource$Projects$Locations$Clusters$Upgrade, options?: MethodOptions): GaxiosPromise<Schema$Operation>;
+        upgrade(params: Params$Resource$Projects$Locations$Clusters$Upgrade, options: StreamMethodOptions | BodyResponseCallback<Readable>, callback: BodyResponseCallback<Readable>): void;
+        upgrade(params: Params$Resource$Projects$Locations$Clusters$Upgrade, options: MethodOptions | BodyResponseCallback<Schema$Operation>, callback: BodyResponseCallback<Schema$Operation>): void;
+        upgrade(params: Params$Resource$Projects$Locations$Clusters$Upgrade, callback: BodyResponseCallback<Schema$Operation>): void;
+        upgrade(callback: BodyResponseCallback<Schema$Operation>): void;
     }
     export interface Params$Resource$Projects$Locations$Clusters$Create extends StandardParameters {
         /**
@@ -2294,11 +2855,11 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2316,11 +2877,11 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2342,14 +2903,24 @@ export declare namespace alloydb_v1beta {
          */
         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 {
         /**
          * Required. The name of the resource. For the required format, see the comment on the Cluster.name field.
@@ -2360,6 +2931,16 @@ export declare namespace alloydb_v1beta {
          */
         view?: string;
     }
+    export interface Params$Resource$Projects$Locations$Clusters$Import extends StandardParameters {
+        /**
+         * Required. The resource name of the cluster.
+         */
+        name?: string;
+        /**
+         * Request body metadata
+         */
+        requestBody?: Schema$ImportClusterRequest;
+    }
     export interface Params$Resource$Projects$Locations$Clusters$List extends StandardParameters {
         /**
          * Optional. Filtering results
@@ -2392,7 +2973,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2400,7 +2981,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2428,6 +3009,16 @@ export declare namespace alloydb_v1beta {
          */
         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 {
         /**
          * Required. The name of the resource. For the required format, see the comment on the Cluster.name field
@@ -2438,6 +3029,16 @@ export declare namespace alloydb_v1beta {
          */
         requestBody?: Schema$SwitchoverClusterRequest;
     }
+    export interface Params$Resource$Projects$Locations$Clusters$Upgrade extends StandardParameters {
+        /**
+         * Required. The resource name of the cluster.
+         */
+        name?: string;
+        /**
+         * Request body metadata
+         */
+        requestBody?: Schema$UpgradeClusterRequest;
+    }
     export class Resource$Projects$Locations$Clusters$Instances {
         context: APIRequestContext;
         constructor(context: APIRequestContext);
@@ -2592,11 +3193,11 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2614,11 +3215,11 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2636,11 +3237,11 @@ export declare namespace alloydb_v1beta {
          */
         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;
     }
@@ -2670,7 +3271,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
     }
@@ -2716,7 +3317,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2724,7 +3325,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2822,7 +3423,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2844,7 +3445,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2890,7 +3491,7 @@ export declare namespace alloydb_v1beta {
          */
         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;
         /**
@@ -2910,7 +3511,7 @@ export declare namespace alloydb_v1beta {
         context: APIRequestContext;
         constructor(context: APIRequestContext);
         /**
-         * 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`.
@@ -3033,6 +3634,10 @@ export declare namespace alloydb_v1beta {
          * Required. The name of the parent resource. The required format is: * projects/{project\}/locations/{location\} Regardless of the parent specified here, as long it is contains a valid project and location, the service will return a static list of supported flags resources. Note that we do not yet support region-specific flags.
          */
         parent?: string;
+        /**
+         * Optional. The scope for which supported flags are requested. If not specified, default is DATABASE.
+         */
+        scope?: string;
     }
     export {};
 }