google-api-python-client 2.155.0__py2.py3-none-any.whl → 2.156.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/serviceconsumermanagement.v1beta1.json

@@ -715,7 +715,7 @@
 }
 }
 },
-"revision": "20241115",
+"revision": "20241205",
 "rootUrl": "https://serviceconsumermanagement.googleapis.com/",
 "schemas": {
 "Api": {
@@ -1218,6 +1218,10 @@
 "description": "`Documentation` provides the information for describing a service. Example: documentation: summary: > The Google Calendar API gives access to most calendar features. pages: - name: Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: > ... - selector: google.calendar.Calendar.Put description: > ... Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: [fully.qualified.proto.name][] To override the display text used for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded from doc using the following notation: (-- internal comment --) A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: (== include path/to/file ==) The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.",
 "id": "Documentation",
 "properties": {
+"additionalIamInfo": {
+"description": "Optional information about the IAM configuration. This is typically used to link to documentation about a product's IAM roles and permissions.",
+"type": "string"
+},
 "documentationRootUrl": {
 "description": "The URL to the root of documentation.",
 "type": "string"

googleapiclient/discovery_cache/documents/servicecontrol.v2.json

@@ -169,7 +169,7 @@
 }
 }
 },
-"revision": "20240802",
+"revision": "20241205",
 "rootUrl": "https://servicecontrol.googleapis.com/",
 "schemas": {
 "Api": {
@@ -487,6 +487,14 @@
 "description": "Response message for the Check method.",
 "id": "CheckResponse",
 "properties": {
+"dynamicMetadata": {
+"additionalProperties": {
+"description": "Properties of the object.",
+"type": "any"
+},
+"description": "Optional response metadata that will be emitted as dynamic metadata to be consumed by the caller of ServiceController. For compatibility with the ext_authz interface.",
+"type": "object"
+},
 "headers": {
 "additionalProperties": {
 "type": "string"

googleapiclient/discovery_cache/documents/servicenetworking.v1.json

@@ -1029,7 +1029,7 @@
 }
 }
 },
-"revision": "20241117",
+"revision": "20241212",
 "rootUrl": "https://servicenetworking.googleapis.com/",
 "schemas": {
 "AddDnsRecordSetMetadata": {
@@ -1968,6 +1968,10 @@
 "description": "`Documentation` provides the information for describing a service. Example: documentation: summary: > The Google Calendar API gives access to most calendar features. pages: - name: Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: > ... - selector: google.calendar.Calendar.Put description: > ... Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: [fully.qualified.proto.name][] To override the display text used for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded from doc using the following notation: (-- internal comment --) A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: (== include path/to/file ==) The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.",
 "id": "Documentation",
 "properties": {
+"additionalIamInfo": {
+"description": "Optional information about the IAM configuration. This is typically used to link to documentation about a product's IAM roles and permissions.",
+"type": "string"
+},
 "documentationRootUrl": {
 "description": "The URL to the root of documentation.",
 "type": "string"

googleapiclient/discovery_cache/documents/servicenetworking.v1beta.json

@@ -307,7 +307,7 @@
 }
 }
 },
-"revision": "20241113",
+"revision": "20241212",
 "rootUrl": "https://servicenetworking.googleapis.com/",
 "schemas": {
 "AddDnsRecordSetMetadata": {
@@ -1080,6 +1080,10 @@
 "description": "`Documentation` provides the information for describing a service. Example: documentation: summary: > The Google Calendar API gives access to most calendar features. pages: - name: Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: > ... - selector: google.calendar.Calendar.Put description: > ... Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: [fully.qualified.proto.name][] To override the display text used for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded from doc using the following notation: (-- internal comment --) A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: (== include path/to/file ==) The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.",
 "id": "Documentation",
 "properties": {
+"additionalIamInfo": {
+"description": "Optional information about the IAM configuration. This is typically used to link to documentation about a product's IAM roles and permissions.",
+"type": "string"
+},
 "documentationRootUrl": {
 "description": "The URL to the root of documentation.",
 "type": "string"

googleapiclient/discovery_cache/documents/serviceusage.v1.json

@@ -426,7 +426,7 @@
 }
 }
 },
-"revision": "20241115",
+"revision": "20241205",
 "rootUrl": "https://serviceusage.googleapis.com/",
 "schemas": {
 "AddEnableRulesMetadata": {
@@ -1231,6 +1231,10 @@
 "description": "`Documentation` provides the information for describing a service. Example: documentation: summary: > The Google Calendar API gives access to most calendar features. pages: - name: Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: > ... - selector: google.calendar.Calendar.Put description: > ... Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: [fully.qualified.proto.name][] To override the display text used for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded from doc using the following notation: (-- internal comment --) A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: (== include path/to/file ==) The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.",
 "id": "Documentation",
 "properties": {
+"additionalIamInfo": {
+"description": "Optional information about the IAM configuration. This is typically used to link to documentation about a product's IAM roles and permissions.",
+"type": "string"
+},
 "documentationRootUrl": {
 "description": "The URL to the root of documentation.",
 "type": "string"

googleapiclient/discovery_cache/documents/serviceusage.v1beta1.json

@@ -964,7 +964,7 @@
 }
 }
 },
-"revision": "20241115",
+"revision": "20241205",
 "rootUrl": "https://serviceusage.googleapis.com/",
 "schemas": {
 "AddEnableRulesMetadata": {
@@ -1808,6 +1808,10 @@
 "description": "`Documentation` provides the information for describing a service. Example: documentation: summary: > The Google Calendar API gives access to most calendar features. pages: - name: Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: > ... - selector: google.calendar.Calendar.Put description: > ... Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: [fully.qualified.proto.name][] To override the display text used for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded from doc using the following notation: (-- internal comment --) A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: (== include path/to/file ==) The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.",
 "id": "Documentation",
 "properties": {
+"additionalIamInfo": {
+"description": "Optional information about the IAM configuration. This is typically used to link to documentation about a product's IAM roles and permissions.",
+"type": "string"
+},
 "documentationRootUrl": {
 "description": "The URL to the root of documentation.",
 "type": "string"

googleapiclient/discovery_cache/documents/sheets.v4.json

@@ -870,7 +870,7 @@
 }
 }
 },
-"revision": "20241008",
+"revision": "20241203",
 "rootUrl": "https://sheets.googleapis.com/",
 "schemas": {
 "AddBandingRequest": {
@@ -6538,6 +6538,10 @@
 "description": "Sets a data validation rule to every cell in the range. To clear validation in a range, call this with no rule specified.",
 "id": "SetDataValidationRequest",
 "properties": {
+"filteredRowsIncluded": {
+"description": "Optional. If true, the data validation rule will be applied to the filtered rows as well.",
+"type": "boolean"
+},
 "range": {
 "$ref": "GridRange",
 "description": "The range the data validation rule should apply to."

googleapiclient/discovery_cache/documents/solar.v1.json

@@ -299,7 +299,7 @@
 }
 }
 },
-"revision": "20240820",
+"revision": "20241211",
 "rootUrl": "https://solar.googleapis.com/",
 "schemas": {
 "BuildingInsights": {
@@ -345,7 +345,7 @@
 "type": "string"
 },
 "name": {
-"description": "The resource name for the building, of the format `building/`.",
+"description": "The resource name for the building, of the format `buildings/{place_id}`.",
 "type": "string"
 },
 "postalCode": {

googleapiclient/discovery_cache/documents/sqladmin.v1.json

@@ -1193,7 +1193,7 @@
 ],
 "parameters": {
 "failover": {
-"description": "Set to true to invoke a replica failover to the designated DR replica. As part of replica failover, the promote operation attempts to add the original primary instance as a replica of the promoted DR replica when the original primary instance comes back online. If set to false or not specified, then the original primary instance becomes an independent Cloud SQL primary instance. Only applicable to MySQL.",
+"description": "Set to true to invoke a replica failover to the DR replica. As part of replica failover, the promote operation attempts to add the original primary instance as a replica of the promoted DR replica when the original primary instance comes back online. If set to false or not specified, then the original primary instance becomes an independent Cloud SQL primary instance.",
 "location": "query",
 "type": "boolean"
 },
@@ -1485,7 +1485,7 @@
 ]
 },
 "switchover": {
-"description": "Switches over from the primary instance to the designated DR replica instance.",
+"description": "Switches over from the primary instance to the DR replica instance.",
 "flatPath": "v1/projects/{project}/instances/{instance}/switchover",
 "httpMethod": "POST",
 "id": "sql.instances.switchover",
@@ -1495,7 +1495,7 @@
 ],
 "parameters": {
 "dbTimeout": {
-"description": "Optional. (MySQL only) Cloud SQL instance operations timeout, which is a sum of all database operations. Default value is 10 minutes and can be modified to a maximum value of 24 hours.",
+"description": "Optional. (MySQL and PostgreSQL only) Cloud SQL instance operations timeout, which is a sum of all database operations. Default value is 10 minutes and can be modified to a maximum value of 24 hours.",
 "format": "google-duration",
 "location": "query",
 "type": "string"
@@ -2366,7 +2366,7 @@
 }
 }
 },
-"revision": "20241108",
+"revision": "20241204",
 "rootUrl": "https://sqladmin.googleapis.com/",
 "schemas": {
 "AclEntry": {
@@ -2856,6 +2856,13 @@ false
 ],
 "type": "string"
 },
+"customSubjectAlternativeNames": {
+"description": "Custom subject alternative names for the server certificate.",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
 "databaseVersion": {
 "description": "The database engine type and version. The `databaseVersion` field cannot be changed after instance creation. MySQL instances: `MYSQL_8_0`, `MYSQL_5_7` (default), or `MYSQL_5_6`. PostgreSQL instances: `POSTGRES_9_6`, `POSTGRES_10`, `POSTGRES_11`, `POSTGRES_12` (default), `POSTGRES_13`, or `POSTGRES_14`. SQL Server instances: `SQLSERVER_2017_STANDARD` (default), `SQLSERVER_2017_ENTERPRISE`, `SQLSERVER_2017_EXPRESS`, `SQLSERVER_2017_WEB`, `SQLSERVER_2019_STANDARD`, `SQLSERVER_2019_ENTERPRISE`, `SQLSERVER_2019_EXPRESS`, or `SQLSERVER_2019_WEB`.",
 "enum": [
@@ -3448,7 +3455,7 @@ false
 },
 "replicationCluster": {
 "$ref": "ReplicationCluster",
-"description": "Optional. A primary instance and disaster recovery (DR) replica pair. A DR replica is a cross-region replica that you designate for failover in the event that the primary instance experiences regional failure. Only applicable to MySQL."
+"description": "Optional. A primary instance and disaster recovery (DR) replica pair. A DR replica is a cross-region replica that you designate for failover in the event that the primary instance experiences regional failure. Applicable to MySQL and PostgreSQL."
 },
 "rootPassword": {
 "description": "Initial root password. Use only on creation. You must set root passwords before you can connect to PostgreSQL instances.",
@@ -3559,6 +3566,13 @@ true
 "description": "Input only. Whether Cloud SQL is enabled to switch storing point-in-time recovery log files from a data disk to Cloud Storage.",
 "type": "boolean"
 },
+"tags": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Optional. Input only. Immutable. Tag keys and tag values that are bound to this instance. You must represent each item in the map as: `\"\" : \"\"`. For example, a single resource can have the following tags: ``` \"123/environment\": \"production\", \"123/costCenter\": \"marketing\", ``` For more information on tag creation and management, see https://cloud.google.com/resource-manager/docs/tags/tags-overview.",
+"type": "object"
+},
 "upgradableDatabaseVersions": {
 "description": "Output only. All database versions that are available for upgrade.",
 "items": {
@@ -4681,6 +4695,13 @@ false
 },
 "type": "array"
 },
+"customSubjectAlternativeNames": {
+"description": "Optional. Custom Subject Alternative Name(SAN)s for a Cloud SQL instance.",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
 "enablePrivatePathForGoogleCloudServices": {
 "description": "Controls connectivity to private IP instances from Google services, such as BigQuery.",
 "type": "boolean"
@@ -4706,15 +4727,21 @@ false
 "enum": [
 "CA_MODE_UNSPECIFIED",
 "GOOGLE_MANAGED_INTERNAL_CA",
-"GOOGLE_MANAGED_CAS_CA"
+"GOOGLE_MANAGED_CAS_CA",
+"CUSTOMER_MANAGED_CAS_CA"
 ],
 "enumDescriptions": [
 "CA mode is unspecified. It is effectively the same as `GOOGLE_MANAGED_INTERNAL_CA`.",
 "Google-managed self-signed internal CA.",
-"Google-managed regional CA part of root CA hierarchy hosted on Google Cloud's Certificate Authority Service (CAS)."
+"Google-managed regional CA part of root CA hierarchy hosted on Google Cloud's Certificate Authority Service (CAS).",
+"Customer-managed CA hosted on Google Cloud's Certificate Authority Service (CAS)."
 ],
 "type": "string"
 },
+"serverCaPool": {
+"description": "Optional. The resource name of the server CA pool for an instance with `CUSTOMER_MANAGED_CAS_CA` as the `server_ca_mode`. Format: projects//locations//caPools/",
+"type": "string"
+},
 "sslMode": {
 "description": "Specify how SSL/TLS is enforced in database connections. If you must use the `require_ssl` flag for backward compatibility, then only the following value pairs are valid: For PostgreSQL and MySQL: * `ssl_mode=ALLOW_UNENCRYPTED_AND_ENCRYPTED` and `require_ssl=false` * `ssl_mode=ENCRYPTED_ONLY` and `require_ssl=false` * `ssl_mode=TRUSTED_CLIENT_CERTIFICATE_REQUIRED` and `require_ssl=true` For SQL Server: * `ssl_mode=ALLOW_UNENCRYPTED_AND_ENCRYPTED` and `require_ssl=false` * `ssl_mode=ENCRYPTED_ONLY` and `require_ssl=true` The value of `ssl_mode` has priority over the value of `require_ssl`. For example, for the pair `ssl_mode=ENCRYPTED_ONLY` and `require_ssl=false`, `ssl_mode=ENCRYPTED_ONLY` means accept only SSL connections, while `require_ssl=false` means accept both non-SSL and SSL connections. In this case, MySQL and PostgreSQL databases respect `ssl_mode` and accepts only SSL connections.",
 "enum": [
@@ -5184,6 +5211,10 @@ false
 ],
 "type": "string"
 },
+"subOperationType": {
+"$ref": "SqlSubOperationType",
+"description": "Optional. The sub operation based on the operation type."
+},
 "targetId": {
 "description": "Name of the database instance related to this operation.",
 "type": "string"
@@ -5249,7 +5280,7 @@ false
 "type": "string"
 },
 "cancelRequested": {
-"description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have been cancelled successfully have Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
+"description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have been cancelled successfully have google.longrunning.Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.",
 "readOnly": true,
 "type": "boolean"
 },
@@ -5456,7 +5487,7 @@ false
 "type": "object"
 },
 "ReplicationCluster": {
-"description": "A primary instance and disaster recovery (DR) replica pair. A DR replica is a cross-region replica that you designate for failover in the event that the primary instance experiences regional failure. Only applicable to MySQL.",
+"description": "A primary instance and disaster recovery (DR) replica pair. A DR replica is a cross-region replica that you designate for failover in the event that the primary instance experiences regional failure. Applicable to MySQL and PostgreSQL.",
 "id": "ReplicationCluster",
 "properties": {
 "drReplica": {
@@ -5469,7 +5500,7 @@ false
 "type": "string"
 },
 "psaWriteEndpoint": {
-"description": "Output only. If set, it indicates this instance has a private service access (PSA) dns endpoint that is pointing to the primary instance of the cluster. If this instance is the primary, the dns should be pointing to this instance. After Switchover or Replica failover, this DNS endpoint points to the promoted instance. This is a read-only field, returned to the user as information. This field can exist even if a standalone instance does not yet have a replica, or had a DR replica that was deleted.",
+"description": "Output only. If set, this field indicates this instance has a private service access (PSA) DNS endpoint that is pointing to the primary instance of the cluster. If this instance is the primary, then the DNS endpoint points to this instance. After a switchover or replica failover operation, this DNS endpoint points to the promoted instance. This is a read-only field, returned to the user as information. This field can exist even if a standalone instance doesn't have a DR replica yet or the DR replica is deleted.",
 "readOnly": true,
 "type": "string"
 }
@@ -6300,6 +6331,31 @@ true
 },
 "type": "object"
 },
+"SqlSubOperationType": {
+"description": "The sub operation type based on the operation type.",
+"id": "SqlSubOperationType",
+"properties": {
+"maintenanceType": {
+"description": "The type of maintenance to be performed on the instance.",
+"enum": [
+"SQL_MAINTENANCE_TYPE_UNSPECIFIED",
+"INSTANCE_MAINTENANCE",
+"REPLICA_INCLUDED_MAINTENANCE",
+"INSTANCE_SELF_SERVICE_MAINTENANCE",
+"REPLICA_INCLUDED_SELF_SERVICE_MAINTENANCE"
+],
+"enumDescriptions": [
+"Maintenance type is unspecified.",
+"Indicates that a standalone instance is undergoing maintenance. The instance can be either a primary instance or a replica.",
+"Indicates that the primary instance and all of its replicas, including cascading replicas, are undergoing maintenance. Maintenance is performed on groups of replicas first, followed by the primary instance.",
+"Indicates that the standalone instance is undergoing maintenance, initiated by self-service. The instance can be either a primary instance or a replica.",
+"Indicates that the primary instance and all of its replicas are undergoing maintenance, initiated by self-service. Maintenance is performed on groups of replicas first, followed by the primary instance."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "SslCert": {
 "description": "SslCerts Resource",
 "id": "SslCert",

googleapiclient/discovery_cache/documents/sqladmin.v1beta4.json

@@ -1193,7 +1193,7 @@
 ],
 "parameters": {
 "failover": {
-"description": "Set to true to invoke a replica failover to the designated DR replica. As part of replica failover, the promote operation attempts to add the original primary instance as a replica of the promoted DR replica when the original primary instance comes back online. If set to false or not specified, then the original primary instance becomes an independent Cloud SQL primary instance. Only applicable to MySQL.",
+"description": "Set to true to invoke a replica failover to the DR replica. As part of replica failover, the promote operation attempts to add the original primary instance as a replica of the promoted DR replica when the original primary instance comes back online. If set to false or not specified, then the original primary instance becomes an independent Cloud SQL primary instance.",
 "location": "query",
 "type": "boolean"
 },
@@ -1485,7 +1485,7 @@
 ]
 },
 "switchover": {
-"description": "Switches over from the primary instance to the designated DR replica instance.",
+"description": "Switches over from the primary instance to the DR replica instance.",
 "flatPath": "sql/v1beta4/projects/{project}/instances/{instance}/switchover",
 "httpMethod": "POST",
 "id": "sql.instances.switchover",
@@ -1495,7 +1495,7 @@
 ],
 "parameters": {
 "dbTimeout": {
-"description": "Optional. (MySQL only) Cloud SQL instance operations timeout, which is a sum of all database operations. Default value is 10 minutes and can be modified to a maximum value of 24 hours.",
+"description": "Optional. (MySQL and PostgreSQL only) Cloud SQL instance operations timeout, which is a sum of all database operations. Default value is 10 minutes and can be modified to a maximum value of 24 hours.",
 "format": "google-duration",
 "location": "query",
 "type": "string"
@@ -2366,7 +2366,7 @@
 }
 }
 },
-"revision": "20241108",
+"revision": "20241204",
 "rootUrl": "https://sqladmin.googleapis.com/",
 "schemas": {
 "AclEntry": {
@@ -2856,6 +2856,13 @@ false
 ],
 "type": "string"
 },
+"customSubjectAlternativeNames": {
+"description": "Custom subject alternative names for the server certificate.",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
 "databaseVersion": {
 "description": "The database engine type and version. The `databaseVersion` field cannot be changed after instance creation. MySQL instances: `MYSQL_8_0`, `MYSQL_5_7` (default), or `MYSQL_5_6`. PostgreSQL instances: `POSTGRES_9_6`, `POSTGRES_10`, `POSTGRES_11` or `POSTGRES_12` (default), `POSTGRES_13`, or `POSTGRES_14`. SQL Server instances: `SQLSERVER_2017_STANDARD` (default), `SQLSERVER_2017_ENTERPRISE`, `SQLSERVER_2017_EXPRESS`, `SQLSERVER_2017_WEB`, `SQLSERVER_2019_STANDARD`, `SQLSERVER_2019_ENTERPRISE`, `SQLSERVER_2019_EXPRESS`, or `SQLSERVER_2019_WEB`.",
 "enum": [
@@ -3448,7 +3455,7 @@ false
 },
 "replicationCluster": {
 "$ref": "ReplicationCluster",
-"description": "A primary instance and disaster recovery (DR) replica pair. A DR replica is a cross-region replica that you designate for failover in the event that the primary instance experiences regional failure. Only applicable to MySQL."
+"description": "A primary instance and disaster recovery (DR) replica pair. A DR replica is a cross-region replica that you designate for failover in the event that the primary instance experiences regional failure. Applicable to MySQL and PostgreSQL."
 },
 "rootPassword": {
 "description": "Initial root password. Use only on creation. You must set root passwords before you can connect to PostgreSQL instances.",
@@ -3560,6 +3567,13 @@ true
 "description": "Input only. Whether Cloud SQL is enabled to switch storing point-in-time recovery log files from a data disk to Cloud Storage.",
 "type": "boolean"
 },
+"tags": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Optional. Input only. Immutable. Tag keys and tag values that are bound to this instance. You must represent each item in the map as: `\"\" : \"\"`. For example, a single resource can have the following tags: ``` \"123/environment\": \"production\", \"123/costCenter\": \"marketing\", ``` For more information on tag creation and management, see https://cloud.google.com/resource-manager/docs/tags/tags-overview.",
+"type": "object"
+},
 "upgradableDatabaseVersions": {
 "description": "Output only. All database versions that are available for upgrade.",
 "items": {
@@ -4682,6 +4696,13 @@ false
 },
 "type": "array"
 },
+"customSubjectAlternativeNames": {
+"description": "Optional. Custom Subject Alternative Name(SAN)s for a Cloud SQL instance.",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
 "enablePrivatePathForGoogleCloudServices": {
 "description": "Controls connectivity to private IP instances from Google services, such as BigQuery.",
 "type": "boolean"
@@ -4707,15 +4728,21 @@ false
 "enum": [
 "CA_MODE_UNSPECIFIED",
 "GOOGLE_MANAGED_INTERNAL_CA",
-"GOOGLE_MANAGED_CAS_CA"
+"GOOGLE_MANAGED_CAS_CA",
+"CUSTOMER_MANAGED_CAS_CA"
 ],
 "enumDescriptions": [
 "CA mode is unspecified. It is effectively the same as `GOOGLE_MANAGED_INTERNAL_CA`.",
 "Google-managed self-signed internal CA.",
-"Google-managed regional CA part of root CA hierarchy hosted on Google Cloud's Certificate Authority Service (CAS)."
+"Google-managed regional CA part of root CA hierarchy hosted on Google Cloud's Certificate Authority Service (CAS).",
+"Customer-managed CA hosted on Google Cloud's Certificate Authority Service (CAS)."
 ],
 "type": "string"
 },
+"serverCaPool": {
+"description": "Optional. The resource name of the server CA pool for an instance with `CUSTOMER_MANAGED_CAS_CA` as the `server_ca_mode`. Format: projects//locations//caPools/",
+"type": "string"
+},
 "sslMode": {
 "description": "Specify how SSL/TLS is enforced in database connections. If you must use the `require_ssl` flag for backward compatibility, then only the following value pairs are valid: For PostgreSQL and MySQL: * `ssl_mode=ALLOW_UNENCRYPTED_AND_ENCRYPTED` and `require_ssl=false` * `ssl_mode=ENCRYPTED_ONLY` and `require_ssl=false` * `ssl_mode=TRUSTED_CLIENT_CERTIFICATE_REQUIRED` and `require_ssl=true` For SQL Server: * `ssl_mode=ALLOW_UNENCRYPTED_AND_ENCRYPTED` and `require_ssl=false` * `ssl_mode=ENCRYPTED_ONLY` and `require_ssl=true` The value of `ssl_mode` has priority over the value of `require_ssl`. For example, for the pair `ssl_mode=ENCRYPTED_ONLY` and `require_ssl=false`, `ssl_mode=ENCRYPTED_ONLY` means accept only SSL connections, while `require_ssl=false` means accept both non-SSL and SSL connections. In this case, MySQL and PostgreSQL databases respect `ssl_mode` and accepts only SSL connections.",
 "enum": [
@@ -5185,6 +5212,10 @@ false
 ],
 "type": "string"
 },
+"subOperationType": {
+"$ref": "SqlSubOperationType",
+"description": "Optional. The sub operation based on the operation type."
+},
 "targetId": {
 "description": "Name of the database instance related to this operation.",
 "type": "string"
@@ -5250,7 +5281,7 @@ false
 "type": "string"
 },
 "cancelRequested": {
-"description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have been cancelled successfully have Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
+"description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have been cancelled successfully have google.longrunning.Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.",
 "readOnly": true,
 "type": "boolean"
 },
@@ -5457,7 +5488,7 @@ false
 "type": "object"
 },
 "ReplicationCluster": {
-"description": "A primary instance and disaster recovery (DR) replica pair. A DR replica is a cross-region replica that you designate for failover in the event that the primary instance has regional failure. Only applicable to MySQL.",
+"description": "A primary instance and disaster recovery (DR) replica pair. A DR replica is a cross-region replica that you designate for failover in the event that the primary instance has regional failure. Applicable to MySQL and PostgreSQL.",
 "id": "ReplicationCluster",
 "properties": {
 "drReplica": {
@@ -5470,7 +5501,7 @@ false
 "type": "string"
 },
 "psaWriteEndpoint": {
-"description": "Output only. If set, it indicates this instance has a private service access (PSA) dns endpoint that is pointing to the primary instance of the cluster. If this instance is the primary, the dns should be pointing to this instance. After Switchover or Replica failover, this DNS endpoint points to the promoted instance. This is a read-only field, returned to the user as information. This field can exist even if a standalone instance does not yet have a replica, or had a DR replica that was deleted.",
+"description": "Output only. If set, this field indicates this instance has a private service access (PSA) DNS endpoint that is pointing to the primary instance of the cluster. If this instance is the primary, then the DNS endpoint points to this instance. After a switchover or replica failover operation, this DNS endpoint points to the promoted instance. This is a read-only field, returned to the user as information. This field can exist even if a standalone instance doesn't have a DR replica yet or the DR replica is deleted.",
 "readOnly": true,
 "type": "string"
 }
@@ -6299,6 +6330,31 @@ true
 },
 "type": "object"
 },
+"SqlSubOperationType": {
+"description": "The sub operation type based on the operation type.",
+"id": "SqlSubOperationType",
+"properties": {
+"maintenanceType": {
+"description": "The type of maintenance to be performed on the instance.",
+"enum": [
+"SQL_MAINTENANCE_TYPE_UNSPECIFIED",
+"INSTANCE_MAINTENANCE",
+"REPLICA_INCLUDED_MAINTENANCE",
+"INSTANCE_SELF_SERVICE_MAINTENANCE",
+"REPLICA_INCLUDED_SELF_SERVICE_MAINTENANCE"
+],
+"enumDescriptions": [
+"Maintenance type is unspecified.",
+"Indicates that a standalone instance is undergoing maintenance. The instance can be either a primary instance or a replica.",
+"Indicates that the primary instance and all of its replicas, including cascading replicas, are undergoing maintenance. Maintenance is performed on groups of replicas first, followed by the primary instance.",
+"Indicates that the standalone instance is undergoing maintenance, initiated by self-service. The instance can be either a primary instance or a replica.",
+"Indicates that the primary instance and all of its replicas are undergoing maintenance, initiated by self-service. Maintenance is performed on groups of replicas first, followed by the primary instance."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "SslCert": {
 "description": "SslCerts Resource",
 "id": "SslCert",