google-api-python-client 2.150.0__py2.py3-none-any.whl → 2.152.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/spanner.v1.json

@@ -39,6 +39,11 @@
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://spanner.us-central2.rep.googleapis.com/",
+"location": "us-central2"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://spanner.us-east1.rep.googleapis.com/",
 "location": "us-east1"
 },
@@ -54,6 +59,11 @@
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://spanner.us-east7.rep.googleapis.com/",
+"location": "us-east7"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://spanner.us-south1.rep.googleapis.com/",
 "location": "us-south1"
 },
@@ -69,6 +79,11 @@
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://spanner.us-west3.rep.googleapis.com/",
+"location": "us-west3"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://spanner.us-west4.rep.googleapis.com/",
 "location": "us-west4"
 },
@@ -1029,7 +1044,7 @@
 "type": "string"
 },
 "encryptionConfig.kmsKeyNames": {
-"description": "Optional. Specifies the KMS configuration for the one or more keys used to protect the backup. Values are of the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by kms_key_names must fully cover all regions of the backup's instance configuration. Some examples: * For single region instance configs, specify a single regional location KMS key. * For multi-regional instance configs of type GOOGLE_MANAGED, either specify a multi-regional location KMS key or multiple regional location KMS keys that cover all regions in the instance config. * For an instance config of type USER_MANAGED, please specify only regional location KMS keys to cover each region in the instance config. Multi-regional location KMS keys are not supported for USER_MANAGED instance configs.",
+"description": "Optional. Specifies the KMS configuration for the one or more keys used to protect the backup. Values are of the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by `kms_key_names` must fully cover all regions of the backup's instance configuration. Some examples: * For regional (single-region) instance configurations, specify a regional location KMS key. * For multi-region instance configurations of type `GOOGLE_MANAGED`, either specify a multi-region location KMS key or multiple regional location KMS keys that cover all regions in the instance configuration. * For an instance configuration of type `USER_MANAGED`, specify only regional location KMS keys to cover each region in the instance configuration. Multi-region location KMS keys aren't supported for `USER_MANAGED` type instance configurations.",
 "location": "query",
 "repeated": true,
 "type": "string"
@@ -1107,7 +1122,7 @@
 ]
 },
 "getIamPolicy": {
-"description": "Gets the access control policy for a database or backup resource. Returns an empty policy if a database or backup exists but does not have a policy set. Authorization requires `spanner.databases.getIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.getIamPolicy` permission on resource.",
+"description": "Gets the access control policy for a database or backup resource. Returns an empty policy if a database or backup exists but does not have a policy set. Authorization requires `spanner.databases.getIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.getIamPolicy` permission on resource. For backup schedules, authorization requires `spanner.backupSchedules.getIamPolicy` permission on resource.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/backups/{backupsId}:getIamPolicy",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.backups.getIamPolicy",
@@ -1213,7 +1228,7 @@
 ]
 },
 "setIamPolicy": {
-"description": "Sets the access control policy on a database or backup resource. Replaces any existing policy. Authorization requires `spanner.databases.setIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.setIamPolicy` permission on resource.",
+"description": "Sets the access control policy on a database or backup resource. Replaces any existing policy. Authorization requires `spanner.databases.setIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.setIamPolicy` permission on resource. For backup schedules, authorization requires `spanner.backupSchedules.setIamPolicy` permission on resource.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/backups/{backupsId}:setIamPolicy",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.backups.setIamPolicy",
@@ -1242,7 +1257,7 @@
 ]
 },
 "testIamPermissions": {
-"description": "Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has `spanner.databases.list` permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has `spanner.backups.list` permission on the containing instance.",
+"description": "Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has `spanner.databases.list` permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has `spanner.backups.list` permission on the containing instance. Calling this method on a backup schedule that does not exist will result in a NOT_FOUND error if the user has `spanner.backupSchedules.list` permission on the containing database.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/backups/{backupsId}:testIamPermissions",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.backups.testIamPermissions",
@@ -1410,7 +1425,7 @@
 ],
 "parameters": {
 "filter": {
-"description": "An expression that filters the list of returned operations. A filter expression consists of a field name, a comparison operator, and a value for filtering. The value must be a string, a number, or a boolean. The comparison operator must be one of: `<`, `>`, `<=`, `>=`, `!=`, `=`, or `:`. Colon `:` is the contains operator. Filter rules are not case sensitive. The following fields in the Operation are eligible for filtering: * `name` - The name of the long-running operation * `done` - False if the operation is in progress, else true. * `metadata.@type` - the type of metadata. For example, the type string for RestoreDatabaseMetadata is `type.googleapis.com/google.spanner.admin.database.v1.RestoreDatabaseMetadata`. * `metadata.` - any field in metadata.value. `metadata.@type` must be specified first, if filtering on metadata fields. * `error` - Error associated with the long-running operation. * `response.@type` - the type of response. * `response.` - any field in response.value. You can combine multiple expressions by enclosing each expression in parentheses. By default, expressions are combined with AND logic. However, you can specify AND, OR, and NOT logic explicitly. Here are a few examples: * `done:true` - The operation is complete. * `(metadata.@type=type.googleapis.com/google.spanner.admin.database.v1.RestoreDatabaseMetadata) AND` \\ `(metadata.source_type:BACKUP) AND` \\ `(metadata.backup_info.backup:backup_howl) AND` \\ `(metadata.name:restored_howl) AND` \\ `(metadata.progress.start_time < \\\"2018-03-28T14:50:00Z\\\") AND` \\ `(error:*)` - Return operations where: * The operation's metadata type is RestoreDatabaseMetadata. * The database is restored from a backup. * The backup name contains \"backup_howl\". * The restored database's name contains \"restored_howl\". * The operation started before 2018-03-28T14:50:00Z. * The operation resulted in an error.",
+"description": "An expression that filters the list of returned operations. A filter expression consists of a field name, a comparison operator, and a value for filtering. The value must be a string, a number, or a boolean. The comparison operator must be one of: `<`, `>`, `<=`, `>=`, `!=`, `=`, or `:`. Colon `:` is the contains operator. Filter rules are not case sensitive. The following fields in the operation are eligible for filtering: * `name` - The name of the long-running operation * `done` - False if the operation is in progress, else true. * `metadata.@type` - the type of metadata. For example, the type string for RestoreDatabaseMetadata is `type.googleapis.com/google.spanner.admin.database.v1.RestoreDatabaseMetadata`. * `metadata.` - any field in metadata.value. `metadata.@type` must be specified first, if filtering on metadata fields. * `error` - Error associated with the long-running operation. * `response.@type` - the type of response. * `response.` - any field in response.value. You can combine multiple expressions by enclosing each expression in parentheses. By default, expressions are combined with AND logic. However, you can specify AND, OR, and NOT logic explicitly. Here are a few examples: * `done:true` - The operation is complete. * `(metadata.@type=type.googleapis.com/google.spanner.admin.database.v1.RestoreDatabaseMetadata) AND` \\ `(metadata.source_type:BACKUP) AND` \\ `(metadata.backup_info.backup:backup_howl) AND` \\ `(metadata.name:restored_howl) AND` \\ `(metadata.progress.start_time < \\\"2018-03-28T14:50:00Z\\\") AND` \\ `(error:*)` - Return operations where: * The operation's metadata type is RestoreDatabaseMetadata. * The database is restored from a backup. * The backup name contains \"backup_howl\". * The restored database's name contains \"restored_howl\". * The operation started before 2018-03-28T14:50:00Z. * The operation resulted in an error.",
 "location": "query",
 "type": "string"
 },
@@ -1583,7 +1598,7 @@
 ]
 },
 "getIamPolicy": {
-"description": "Gets the access control policy for a database or backup resource. Returns an empty policy if a database or backup exists but does not have a policy set. Authorization requires `spanner.databases.getIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.getIamPolicy` permission on resource.",
+"description": "Gets the access control policy for a database or backup resource. Returns an empty policy if a database or backup exists but does not have a policy set. Authorization requires `spanner.databases.getIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.getIamPolicy` permission on resource. For backup schedules, authorization requires `spanner.backupSchedules.getIamPolicy` permission on resource.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}:getIamPolicy",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.databases.getIamPolicy",
@@ -1766,7 +1781,7 @@
 ]
 },
 "setIamPolicy": {
-"description": "Sets the access control policy on a database or backup resource. Replaces any existing policy. Authorization requires `spanner.databases.setIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.setIamPolicy` permission on resource.",
+"description": "Sets the access control policy on a database or backup resource. Replaces any existing policy. Authorization requires `spanner.databases.setIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.setIamPolicy` permission on resource. For backup schedules, authorization requires `spanner.backupSchedules.setIamPolicy` permission on resource.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}:setIamPolicy",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.databases.setIamPolicy",
@@ -1795,7 +1810,7 @@
 ]
 },
 "testIamPermissions": {
-"description": "Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has `spanner.databases.list` permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has `spanner.backups.list` permission on the containing instance.",
+"description": "Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has `spanner.databases.list` permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has `spanner.backups.list` permission on the containing instance. Calling this method on a backup schedule that does not exist will result in a NOT_FOUND error if the user has `spanner.backupSchedules.list` permission on the containing database.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}:testIamPermissions",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.databases.testIamPermissions",
@@ -1943,7 +1958,7 @@
 ]
 },
 "getIamPolicy": {
-"description": "Gets the access control policy for a database or backup resource. Returns an empty policy if a database or backup exists but does not have a policy set. Authorization requires `spanner.databases.getIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.getIamPolicy` permission on resource.",
+"description": "Gets the access control policy for a database or backup resource. Returns an empty policy if a database or backup exists but does not have a policy set. Authorization requires `spanner.databases.getIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.getIamPolicy` permission on resource. For backup schedules, authorization requires `spanner.backupSchedules.getIamPolicy` permission on resource.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}/backupSchedules/{backupSchedulesId}:getIamPolicy",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.databases.backupSchedules.getIamPolicy",
@@ -2044,7 +2059,7 @@
 ]
 },
 "setIamPolicy": {
-"description": "Sets the access control policy on a database or backup resource. Replaces any existing policy. Authorization requires `spanner.databases.setIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.setIamPolicy` permission on resource.",
+"description": "Sets the access control policy on a database or backup resource. Replaces any existing policy. Authorization requires `spanner.databases.setIamPolicy` permission on resource. For backups, authorization requires `spanner.backups.setIamPolicy` permission on resource. For backup schedules, authorization requires `spanner.backupSchedules.setIamPolicy` permission on resource.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}/backupSchedules/{backupSchedulesId}:setIamPolicy",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.databases.backupSchedules.setIamPolicy",
@@ -2073,7 +2088,7 @@
 ]
 },
 "testIamPermissions": {
-"description": "Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has `spanner.databases.list` permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has `spanner.backups.list` permission on the containing instance.",
+"description": "Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has `spanner.databases.list` permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has `spanner.backups.list` permission on the containing instance. Calling this method on a backup schedule that does not exist will result in a NOT_FOUND error if the user has `spanner.backupSchedules.list` permission on the containing database.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}/backupSchedules/{backupSchedulesId}:testIamPermissions",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.databases.backupSchedules.testIamPermissions",
@@ -2143,7 +2158,7 @@
 ]
 },
 "testIamPermissions": {
-"description": "Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has `spanner.databases.list` permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has `spanner.backups.list` permission on the containing instance.",
+"description": "Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has `spanner.databases.list` permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has `spanner.backups.list` permission on the containing instance. Calling this method on a backup schedule that does not exist will result in a NOT_FOUND error if the user has `spanner.backupSchedules.list` permission on the containing database.",
 "flatPath": "v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}/databaseRoles/{databaseRolesId}:testIamPermissions",
 "httpMethod": "POST",
 "id": "spanner.projects.instances.databases.databaseRoles.testIamPermissions",
@@ -3304,13 +3319,35 @@
 }
 }
 },
-"revision": "20240930",
+"revision": "20241020",
 "rootUrl": "https://spanner.googleapis.com/",
 "schemas": {
+"AsymmetricAutoscalingOption": {
+"description": "AsymmetricAutoscalingOption specifies the scaling of replicas identified by the given selection.",
+"id": "AsymmetricAutoscalingOption",
+"properties": {
+"overrides": {
+"$ref": "AutoscalingConfigOverrides",
+"description": "Optional. Overrides applied to the top-level autoscaling configuration for the selected replicas."
+},
+"replicaSelection": {
+"$ref": "InstanceReplicaSelection",
+"description": "Required. Selects the replicas to which this AsymmetricAutoscalingOption applies. Only read-only replicas are supported."
+}
+},
+"type": "object"
+},
 "AutoscalingConfig": {
 "description": "Autoscaling configuration for an instance.",
 "id": "AutoscalingConfig",
 "properties": {
+"asymmetricAutoscalingOptions": {
+"description": "Optional. Optional asymmetric autoscaling options. Replicas matching the replica selection criteria will be autoscaled independently from other replicas. The autoscaler will scale the replicas based on the utilization of replicas identified by the replica selection. Replica selections should not overlap with each other. Other replicas (those do not match any replica selection) will be autoscaled together and will have the same compute capacity allocated to them.",
+"items": {
+"$ref": "AsymmetricAutoscalingOption"
+},
+"type": "array"
+},
 "autoscalingLimits": {
 "$ref": "AutoscalingLimits",
 "description": "Required. Autoscaling limits for an instance."
@@ -3322,6 +3359,22 @@
 },
 "type": "object"
 },
+"AutoscalingConfigOverrides": {
+"description": "Overrides the top-level autoscaling configuration for the replicas identified by `replica_selection`. All fields in this message are optional. Any unspecified fields will use the corresponding values from the top-level autoscaling configuration.",
+"id": "AutoscalingConfigOverrides",
+"properties": {
+"autoscalingLimits": {
+"$ref": "AutoscalingLimits",
+"description": "Optional. If specified, overrides the min/max limit in the top-level autoscaling configuration for the selected replicas."
+},
+"autoscalingTargetHighPriorityCpuUtilizationPercent": {
+"description": "Optional. If specified, overrides the autoscaling target high_priority_cpu_utilization_percent in the top-level autoscaling configuration for the selected replicas.",
+"format": "int32",
+"type": "integer"
+}
+},
+"type": "object"
+},
 "AutoscalingLimits": {
 "description": "The autoscaling limits for the instance. Users can define the minimum and maximum compute capacity allocated to the instance, and the autoscaler will only scale within that range. Users can either use nodes or processing units to specify the limits, but should use the same unit to set both the min_limit and max_limit.",
 "id": "AutoscalingLimits",
@@ -3409,7 +3462,7 @@
 "readOnly": true
 },
 "encryptionInformation": {
-"description": "Output only. The encryption information for the backup, whether it is protected by one or more KMS keys. The information includes all Cloud KMS key versions used to encrypt the backup. The `encryption_status' field inside of each `EncryptionInfo` is not populated. At least one of the key versions must be available for the backup to be restored. If a key version is revoked in the middle of a restore, the restore behavior is undefined.",
+"description": "Output only. The encryption information for the backup, whether it is protected by one or more KMS keys. The information includes all Cloud KMS key versions used to encrypt the backup. The `encryption_status` field inside of each `EncryptionInfo` is not populated. At least one of the key versions must be available for the backup to be restored. If a key version is revoked in the middle of a restore, the restore behavior is undefined.",
 "items": {
 "$ref": "EncryptionInfo"
 },
@@ -3653,6 +3706,10 @@
 "description": "The request for BeginTransaction.",
 "id": "BeginTransactionRequest",
 "properties": {
+"mutationKey": {
+"$ref": "Mutation",
+"description": "Optional. Required for read-write transactions on a multiplexed session that commit mutations but do not perform any reads or queries. Clients should randomly select one of the mutations from the mutation set and send it as a part of this request."
+},
 "options": {
 "$ref": "TransactionOptions",
 "description": "Required. Options for the new transaction."
@@ -3762,6 +3819,10 @@
 },
 "type": "array"
 },
+"precommitToken": {
+"$ref": "MultiplexedSessionPrecommitToken",
+"description": "Optional. If the read-write transaction was executed on a multiplexed session, the precommit token with the highest sequence number received in this transaction attempt, should be included here. Failing to do so will result in a FailedPrecondition error."
+},
 "requestOptions": {
 "$ref": "RequestOptions",
 "description": "Common options for this request."
@@ -3794,6 +3855,10 @@
 "description": "The Cloud Spanner timestamp at which the transaction committed.",
 "format": "google-datetime",
 "type": "string"
+},
+"precommitToken": {
+"$ref": "MultiplexedSessionPrecommitToken",
+"description": "If specified, transaction has not committed yet. Clients must retry the commit with the new precommit token."
 }
 },
 "type": "object"
@@ -3873,7 +3938,7 @@
 "type": "string"
 },
 "kmsKeyNames": {
-"description": "Optional. Specifies the KMS configuration for the one or more keys used to protect the backup. Values are of the form `projects//locations//keyRings//cryptoKeys/`. Kms keys specified can be in any order. The keys referenced by kms_key_names must fully cover all regions of the backup's instance configuration. Some examples: * For single region instance configs, specify a single regional location KMS key. * For multi-regional instance configs of type GOOGLE_MANAGED, either specify a multi-regional location KMS key or multiple regional location KMS keys that cover all regions in the instance config. * For an instance config of type USER_MANAGED, please specify only regional location KMS keys to cover each region in the instance config. Multi-regional location KMS keys are not supported for USER_MANAGED instance configs.",
+"description": "Optional. Specifies the KMS configuration for the one or more keys used to protect the backup. Values are of the form `projects//locations//keyRings//cryptoKeys/`. KMS keys specified can be in any order. The keys referenced by `kms_key_names` must fully cover all regions of the backup's instance configuration. Some examples: * For regional (single-region) instance configurations, specify a regional location KMS key. * For multi-region instance configurations of type `GOOGLE_MANAGED`, either specify a multi-region location KMS key or multiple regional location KMS keys that cover all regions in the instance configuration. * For an instance configuration of type `USER_MANAGED`, specify only regional location KMS keys to cover each region in the instance configuration. Multi-region location KMS keys aren't supported for `USER_MANAGED` type instance configurations.",
 "items": {
 "type": "string"
 },
@@ -3955,7 +4020,7 @@
 "type": "string"
 },
 "kmsKeyNames": {
-"description": "Optional. Specifies the KMS configuration for the one or more keys used to protect the backup. Values are of the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by kms_key_names must fully cover all regions of the backup's instance configuration. Some examples: * For single region instance configs, specify a single regional location KMS key. * For multi-regional instance configs of type GOOGLE_MANAGED, either specify a multi-regional location KMS key or multiple regional location KMS keys that cover all regions in the instance config. * For an instance config of type USER_MANAGED, please specify only regional location KMS keys to cover each region in the instance config. Multi-regional location KMS keys are not supported for USER_MANAGED instance configs.",
+"description": "Optional. Specifies the KMS configuration for the one or more keys used to protect the backup. Values are of the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by `kms_key_names` must fully cover all regions of the backup's instance configuration. Some examples: * For regional (single-region) instance configurations, specify a regional location KMS key. * For multi-region instance configurations of type `GOOGLE_MANAGED`, either specify a multi-region location KMS key or multiple regional location KMS keys that cover all regions in the instance configuration. * For an instance configuration of type `USER_MANAGED`, specify only regional location KMS keys to cover each region in the instance configuration. Multi-region location KMS keys aren't supported for `USER_MANAGED` type instance configurations.",
 "items": {
 "type": "string"
 },
@@ -4254,7 +4319,7 @@
 "readOnly": true
 },
 "encryptionInfo": {
-"description": "Output only. For databases that are using customer managed encryption, this field contains the encryption information for the database, such as all Cloud KMS key versions that are in use. The `encryption_status' field inside of each `EncryptionInfo` is not populated. For databases that are using Google default or other types of encryption, this field is empty. This field is propagated lazily from the backend. There might be a delay from when a key version is being used and when it appears in this field.",
+"description": "Output only. For databases that are using customer managed encryption, this field contains the encryption information for the database, such as all Cloud KMS key versions that are in use. The `encryption_status` field inside of each `EncryptionInfo` is not populated. For databases that are using Google default or other types of encryption, this field is empty. This field is propagated lazily from the backend. There might be a delay from when a key version is being used and when it appears in this field.",
 "items": {
 "$ref": "EncryptionInfo"
 },
@@ -4445,7 +4510,7 @@
 "type": "string"
 },
 "kmsKeyNames": {
-"description": "Specifies the KMS configuration for the one or more keys used to encrypt the database. Values are of the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by kms_key_names must fully cover all regions of the database instance configuration. Some examples: * For single region database instance configs, specify a single regional location KMS key. * For multi-regional database instance configs of type GOOGLE_MANAGED, either specify a multi-regional location KMS key or multiple regional location KMS keys that cover all regions in the instance config. * For a database instance config of type USER_MANAGED, please specify only regional location KMS keys to cover each region in the instance config. Multi-regional location KMS keys are not supported for USER_MANAGED instance configs.",
+"description": "Specifies the KMS configuration for one or more keys used to encrypt the database. Values are of the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by `kms_key_names` must fully cover all regions of the database's instance configuration. Some examples: * For regional (single-region) instance configurations, specify a regional location KMS key. * For multi-region instance configurations of type `GOOGLE_MANAGED`, either specify a multi-region location KMS key or multiple regional location KMS keys that cover all regions in the instance configuration. * For an instance configuration of type `USER_MANAGED`, specify only regional location KMS keys to cover each region in the instance configuration. Multi-region location KMS keys aren't supported for `USER_MANAGED` type instance configurations.",
 "items": {
 "type": "string"
 },
@@ -4531,6 +4596,10 @@
 "description": "The response for ExecuteBatchDml. Contains a list of ResultSet messages, one for each DML statement that has successfully executed, in the same order as the statements in the request. If a statement fails, the status in the response body identifies the cause of the failure. To check for DML statements that failed, use the following approach: 1. Check the status in the response message. The google.rpc.Code enum value `OK` indicates that all statements were executed successfully. 2. If the status was not `OK`, check the number of result sets in the response. If the response contains `N` ResultSet messages, then statement `N+1` in the request failed. Example 1: * Request: 5 DML statements, all executed successfully. * Response: 5 ResultSet messages, with the status `OK`. Example 2: * Request: 5 DML statements. The third statement has a syntax error. * Response: 2 ResultSet messages, and a syntax error (`INVALID_ARGUMENT`) status. The number of ResultSet messages indicates that the third statement failed, and the fourth and fifth statements were not executed.",
 "id": "ExecuteBatchDmlResponse",
 "properties": {
+"precommitToken": {
+"$ref": "MultiplexedSessionPrecommitToken",
+"description": "Optional. A precommit token will be included if the read-write transaction is on a multiplexed session. The precommit token with the highest sequence number from this transaction attempt should be passed to the Commit request for this transaction."
+},
 "resultSets": {
 "description": "One ResultSet for each statement in the request that ran successfully, in the same order as the statements in the request. Each ResultSet does not contain any rows. The ResultSetStats in each ResultSet contain the number of rows modified by the statement. Only the first ResultSet in the response contains valid ResultSetMetadata.",
 "items": {
@@ -4582,12 +4651,16 @@
 "enum": [
 "NORMAL",
 "PLAN",
-"PROFILE"
+"PROFILE",
+"WITH_STATS",
+"WITH_PLAN_AND_STATS"
 ],
 "enumDescriptions": [
 "The default mode. Only the statement results are returned.",
 "This mode returns only the query plan, without any results or execution statistics information.",
-"This mode returns the query plan, overall execution statistics, operator level execution statistics along with the results. This has a performance overhead compared to the other modes. It is not recommended to use this mode for production traffic."
+"This mode returns the query plan, overall execution statistics, operator level execution statistics along with the results. This has a performance overhead compared to the other modes. It is not recommended to use this mode for production traffic.",
+"This mode returns the overall (but not operator-level) execution statistics along with the results.",
+"This mode returns the query plan, overall (but not operator-level) execution statistics along with the results."
 ],
 "type": "string"
 },
@@ -4829,6 +4902,20 @@
 "readOnly": true,
 "type": "string"
 },
+"defaultBackupScheduleType": {
+"description": "Optional. Controls the default backup behavior for new databases within the instance. Note that `AUTOMATIC` is not permitted for free instances, as backups and backup schedules are not allowed for free instances. In the `GetInstance` or `ListInstances` response, if the value of default_backup_schedule_type is unset or NONE, no default backup schedule will be created for new databases within the instance.",
+"enum": [
+"DEFAULT_BACKUP_SCHEDULE_TYPE_UNSPECIFIED",
+"NONE",
+"AUTOMATIC"
+],
+"enumDescriptions": [
+"Not specified.",
+"No default backup schedule will be created automatically on creation of a database within the instance.",
+"A default backup schedule will be created automatically on creation of a database within the instance. The default backup schedule creates a full backup every 24 hours and retains the backup for a period of 7 days. Once created, the default backup schedule can be edited/deleted similar to any other backup schedule."
+],
+"type": "string"
+},
 "displayName": {
 "description": "Required. The descriptive name for this instance as it appears in UIs. Must be unique per project and between 4 and 30 characters in length.",
 "type": "string"
@@ -4895,6 +4982,14 @@
 "format": "int32",
 "type": "integer"
 },
+"replicaComputeCapacity": {
+"description": "Output only. Lists the compute capacity per ReplicaSelection. A replica selection identifies a set of replicas with common properties. Replicas identified by a ReplicaSelection are scaled with the same compute capacity.",
+"items": {
+"$ref": "ReplicaComputeCapacity"
+},
+"readOnly": true,
+"type": "array"
+},
 "state": {
 "description": "Output only. The current instance state. For CreateInstance, the state must be either omitted or set to `CREATING`. For UpdateInstance, the state must be either omitted or set to `READY`.",
 "enum": [
@@ -5147,6 +5242,17 @@
 },
 "type": "object"
 },
+"InstanceReplicaSelection": {
+"description": "ReplicaSelection identifies replicas with common properties.",
+"id": "InstanceReplicaSelection",
+"properties": {
+"location": {
+"description": "Required. Name of the location of the replicas (e.g., \"us-central1\").",
+"type": "string"
+}
+},
+"type": "object"
+},
 "KeyRange": {
 "description": "KeyRange represents a range of rows in a table or index. A range has a start key and an end key. These keys can be open or closed, indicating if the range includes rows with that key. Keys are represented by lists, where the ith value in the list corresponds to the ith component of the table or index primary key. Individual values are encoded as described here. For example, consider the following table definition: CREATE TABLE UserEvents ( UserName STRING(MAX), EventDate STRING(10) ) PRIMARY KEY(UserName, EventDate); The following keys name rows in this table: \"Bob\", \"2014-09-23\" Since the `UserEvents` table's `PRIMARY KEY` clause names two columns, each `UserEvents` key has two elements; the first is the `UserName`, and the second is the `EventDate`. Key ranges with multiple components are interpreted lexicographically by component using the table or index key's declared sort order. For example, the following range returns all events for user `\"Bob\"` that occurred in the year 2015: \"start_closed\": [\"Bob\", \"2015-01-01\"] \"end_closed\": [\"Bob\", \"2015-12-31\"] Start and end keys can omit trailing key components. This affects the inclusion and exclusion of rows that exactly match the provided key components: if the key is closed, then rows that exactly match the provided components are included; if the key is open, then rows that exactly match are not included. For example, the following range includes all events for `\"Bob\"` that occurred during and after the year 2000: \"start_closed\": [\"Bob\", \"2000-01-01\"] \"end_closed\": [\"Bob\"] The next example retrieves all events for `\"Bob\"`: \"start_closed\": [\"Bob\"] \"end_closed\": [\"Bob\"] To retrieve events before the year 2000: \"start_closed\": [\"Bob\"] \"end_open\": [\"Bob\", \"2000-01-01\"] The following range includes all rows in the table: \"start_closed\": [] \"end_closed\": [] This range returns all users whose `UserName` begins with any character from A to C: \"start_closed\": [\"A\"] \"end_open\": [\"D\"] This range returns all users whose `UserName` begins with B: \"start_closed\": [\"B\"] \"end_open\": [\"C\"] Key ranges honor column sort order. For example, suppose a table is defined as follows: CREATE TABLE DescendingSortedTable { Key INT64, ... ) PRIMARY KEY(Key DESC); The following range retrieves all rows with key values between 1 and 100 inclusive: \"start_closed\": [\"100\"] \"end_closed\": [\"1\"] Note that 100 is passed as the start, and 1 is passed as the end, because `Key` is a descending column in the schema.",
 "id": "KeyRange",
@@ -5829,6 +5935,10 @@
 "$ref": "ResultSetMetadata",
 "description": "Metadata about the result set, such as row type information. Only present in the first response."
 },
+"precommitToken": {
+"$ref": "MultiplexedSessionPrecommitToken",
+"description": "Optional. A precommit token will be included if the read-write transaction is on a multiplexed session. The precommit token with the highest sequence number from this transaction attempt should be passed to the Commit request for this transaction."
+},
 "resumeToken": {
 "description": "Streaming calls might be interrupted for a variety of reasons, such as TCP connection loss. If this occurs, the stream of results can be resumed by re-sending the original request and including `resume_token`. Note that executing any other transaction in the same session invalidates the token.",
 "format": "byte",
@@ -6304,6 +6414,11 @@
 "description": "Message type to initiate a read-write transaction. Currently this transaction type has no options.",
 "id": "ReadWrite",
 "properties": {
+"multiplexedSessionPreviousTransactionId": {
+"description": "Optional. Clients should pass the transaction ID of the previous transaction attempt that was aborted if this transaction is being executed on a multiplexed session.",
+"format": "byte",
+"type": "string"
+},
 "readLockMode": {
 "description": "Read lock mode for the transaction.",
 "enum": [
@@ -6321,6 +6436,27 @@
 },
 "type": "object"
 },
+"ReplicaComputeCapacity": {
+"description": "ReplicaComputeCapacity describes the amount of server resources that are allocated to each replica identified by the replica selection.",
+"id": "ReplicaComputeCapacity",
+"properties": {
+"nodeCount": {
+"description": "The number of nodes allocated to each replica. This may be zero in API responses for instances that are not yet in state `READY`.",
+"format": "int32",
+"type": "integer"
+},
+"processingUnits": {
+"description": "The number of processing units allocated to each replica. This may be zero in API responses for instances that are not yet in state `READY`.",
+"format": "int32",
+"type": "integer"
+},
+"replicaSelection": {
+"$ref": "InstanceReplicaSelection",
+"description": "Required. Identifies replicas by specified properties. All replicas in the selection have the same amount of compute capacity."
+}
+},
+"type": "object"
+},
 "ReplicaInfo": {
 "id": "ReplicaInfo",
 "properties": {
@@ -6432,7 +6568,7 @@
 "type": "string"
 },
 "kmsKeyNames": {
-"description": "Optional. Specifies the KMS configuration for the one or more keys used to encrypt the database. Values have the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by kms_key_names must fully cover all regions of the database instance configuration. Some examples: * For single region database instance configurations, specify a single regional location KMS key. * For multi-regional database instance configurations of type `GOOGLE_MANAGED`, either specify a multi-regional location KMS key or multiple regional location KMS keys that cover all regions in the instance configuration. * For a database instance configuration of type `USER_MANAGED`, please specify only regional location KMS keys to cover each region in the instance configuration. Multi-regional location KMS keys are not supported for USER_MANAGED instance configurations.",
+"description": "Optional. Specifies the KMS configuration for one or more keys used to encrypt the database. Values have the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by `kms_key_names` must fully cover all regions of the database's instance configuration. Some examples: * For regional (single-region) instance configurations, specify a regional location KMS key. * For multi-region instance configurations of type `GOOGLE_MANAGED`, either specify a multi-region location KMS key or multiple regional location KMS keys that cover all regions in the instance configuration. * For an instance configuration of type `USER_MANAGED`, specify only regional location KMS keys to cover each region in the instance configuration. Multi-region location KMS keys aren't supported for `USER_MANAGED` type instance configurations.",
 "items": {
 "type": "string"
 },
@@ -6531,6 +6667,10 @@
 "$ref": "ResultSetMetadata",
 "description": "Metadata about the result set, such as row type information."
 },
+"precommitToken": {
+"$ref": "MultiplexedSessionPrecommitToken",
+"description": "Optional. A precommit token will be included if the read-write transaction is on a multiplexed session. The precommit token with the highest sequence number from this transaction attempt should be passed to the Commit request for this transaction."
+},
 "rows": {
 "description": "Each element in `rows` is a row whose format is defined by metadata.row_type. The ith element in each row matches the ith field in metadata.row_type. Elements are encoded based on type as described here.",
 "items": {
@@ -6927,7 +7067,8 @@
 "NUMERIC",
 "JSON",
 "PROTO",
-"ENUM"
+"ENUM",
+"INTERVAL"
 ],
 "enumDescriptions": [
 "Not specified.",
@@ -6944,7 +7085,8 @@
 "Encoded as `string`, in decimal format or scientific notation format. Decimal format: `[+-]Digits[.[Digits]]` or `+-.Digits` Scientific notation: `[+-]Digits[.[Digits]][ExponentIndicator[+-]Digits]` or `+-.Digits[ExponentIndicator[+-]Digits]` (ExponentIndicator is `\"e\"` or `\"E\"`)",
 "Encoded as a JSON-formatted `string` as described in RFC 7159. The following rules are applied when parsing JSON input: - Whitespace characters are not preserved. - If a JSON object has duplicate keys, only the first key is preserved. - Members of a JSON object are not guaranteed to have their order preserved. - JSON array elements will have their order preserved.",
 "Encoded as a base64-encoded `string`, as described in RFC 4648, section 4.",
-"Encoded as `string`, in decimal format."
+"Encoded as `string`, in decimal format.",
+"Encoded as `string`, in `ISO8601` duration format - `P[n]Y[n]M[n]DT[n]H[n]M[n[.fraction]]S` where `n` is an integer. For example, `P1Y2M3DT4H5M6.5S` represents time duration of 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6.5 seconds."
 ],
 "type": "string"
 },
@@ -7023,7 +7165,7 @@
 "id": "UpdateDatabaseDdlRequest",
 "properties": {
 "operationId": {
-"description": "If empty, the new update request is assigned an automatically-generated operation ID. Otherwise, `operation_id` is used to construct the name of the resulting Operation. Specifying an explicit operation ID simplifies determining whether the statements were executed in the event that the UpdateDatabaseDdl call is replayed, or the return value is otherwise lost: the database and `operation_id` fields can be combined to form the name of the resulting longrunning.Operation: `/operations/`. `operation_id` should be unique within the database, and must be a valid identifier: `a-z*`. Note that automatically-generated operation IDs always begin with an underscore. If the named operation already exists, UpdateDatabaseDdl returns `ALREADY_EXISTS`.",
+"description": "If empty, the new update request is assigned an automatically-generated operation ID. Otherwise, `operation_id` is used to construct the name of the resulting Operation. Specifying an explicit operation ID simplifies determining whether the statements were executed in the event that the UpdateDatabaseDdl call is replayed, or the return value is otherwise lost: the database and `operation_id` fields can be combined to form the `name` of the resulting longrunning.Operation: `/operations/`. `operation_id` should be unique within the database, and must be a valid identifier: `a-z*`. Note that automatically-generated operation IDs always begin with an underscore. If the named operation already exists, UpdateDatabaseDdl returns `ALREADY_EXISTS`.",
 "type": "string"
 },
 "protoDescriptors": {

googleapiclient/discovery_cache/documents/speech.v1.json

@@ -15,6 +15,23 @@
 "description": "Converts audio to text by applying powerful neural network models.",
 "discoveryVersion": "v1",
 "documentationLink": "https://cloud.google.com/speech-to-text/docs/quickstart-protocol",
+"endpoints": [
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://speech.us-central1.rep.googleapis.com/",
+"location": "us-central1"
+},
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://speech.us-west1.rep.googleapis.com/",
+"location": "us-west1"
+},
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://speech.me-west1.rep.googleapis.com/",
+"location": "me-west1"
+}
+],
 "fullyEncodeReservedExpansion": true,
 "icons": {
 "x16": "http://www.google.com/images/icons/product/search-16.gif",
@@ -524,7 +541,7 @@
 }
 }
 },
-"revision": "20240926",
+"revision": "20241024",
 "rootUrl": "https://speech.googleapis.com/",
 "schemas": {
 "ABNFGrammar": {

googleapiclient/discovery_cache/documents/speech.v1p1beta1.json

@@ -15,6 +15,23 @@
 "description": "Converts audio to text by applying powerful neural network models.",
 "discoveryVersion": "v1",
 "documentationLink": "https://cloud.google.com/speech-to-text/docs/quickstart-protocol",
+"endpoints": [
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://speech.us-central1.rep.googleapis.com/",
+"location": "us-central1"
+},
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://speech.us-west1.rep.googleapis.com/",
+"location": "us-west1"
+},
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://speech.me-west1.rep.googleapis.com/",
+"location": "me-west1"
+}
+],
 "fullyEncodeReservedExpansion": true,
 "icons": {
 "x16": "http://www.google.com/images/icons/product/search-16.gif",
@@ -524,7 +541,7 @@
 }
 }
 },
-"revision": "20240926",
+"revision": "20241024",
 "rootUrl": "https://speech.googleapis.com/",
 "schemas": {
 "ABNFGrammar": {

googleapiclient/discovery_cache/documents/sqladmin.v1.json

@@ -609,7 +609,7 @@
 "instances": {
 "methods": {
 "ListServerCertificates": {
-"description": "Lists all versions of server certificates and certificate authorities (CAs) for the specified instance. There can be up to three sets of certs listed: the certificate that is currently in use, a future that has been added but not yet used to sign a certificate, and a certificate that has been rotated out.",
+"description": "Lists all versions of server certificates and certificate authorities (CAs) for the specified instance. There can be up to three sets of certs listed: the certificate that is currently in use, a future that has been added but not yet used to sign a certificate, and a certificate that has been rotated out. For instances not using Certificate Authority Service (CAS) server CA, use ListServerCas instead.",
 "flatPath": "v1/projects/{project}/instances/{instance}/listServerCertificates",
 "httpMethod": "GET",
 "id": "sql.instances.ListServerCertificates",
@@ -2366,7 +2366,7 @@
 }
 }
 },
-"revision": "20241004",
+"revision": "20241011",
 "rootUrl": "https://sqladmin.googleapis.com/",
 "schemas": {
 "AclEntry": {
@@ -5831,7 +5831,8 @@ true
 "UNSUPPORTED_COLUMNS",
 "USERS_NOT_CREATED_IN_REPLICA",
 "UNSUPPORTED_SYSTEM_OBJECTS",
-"UNSUPPORTED_TABLES_WITH_REPLICA_IDENTITY"
+"UNSUPPORTED_TABLES_WITH_REPLICA_IDENTITY",
+"SELECTED_OBJECTS_NOT_EXIST_ON_SOURCE"
 ],
 "enumDescriptions": [
 "",
@@ -5886,7 +5887,8 @@ true
 "The source database has generated columns that can't be migrated. Please change them to regular columns before migration.",
 "The source database has users that aren't created in the replica. First, create all users, which are in the pg_user_mappings table of the source database, in the destination instance. Then, perform the migration.",
 "The selected objects include system objects that aren't supported for migration.",
-"The source database has tables with the FULL or NOTHING replica identity. Before starting your migration, either remove the identity or change it to DEFAULT. Note that this is an error and will block the migration."
+"The source database has tables with the FULL or NOTHING replica identity. Before starting your migration, either remove the identity or change it to DEFAULT. Note that this is an error and will block the migration.",
+"The selected objects don't exist on the source instance."
 ],
 "type": "string"
 }