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

googleapiclient/discovery_cache/documents/serviceconsumermanagement.v1.json

@@ -108,7 +108,7 @@
 "operations": {
 "methods": {
 "cancel": {
-"description": "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`.",
+"description": "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`.",
 "flatPath": "v1/operations/{operationsId}:cancel",
 "httpMethod": "POST",
 "id": "serviceconsumermanagement.operations.cancel",
@@ -542,7 +542,7 @@
 }
 }
 },
-"revision": "20240929",
+"revision": "20241115",
 "rootUrl": "https://serviceconsumermanagement.googleapis.com/",
 "schemas": {
 "AddTenantProjectRequest": {
@@ -1348,6 +1348,10 @@
 "description": "Experimental features to be included during client library generation. These fields will be deprecated once the feature graduates and is enabled by default.",
 "id": "ExperimentalFeatures",
 "properties": {
+"protobufPythonicTypesEnabled": {
+"description": "Enables generation of protobuf code using new types that are more Pythonic which are included in `protobuf>=5.29.x`. This feature will be enabled by default 1 month after launching the feature in preview packages.",
+"type": "boolean"
+},
 "restAsyncIoEnabled": {
 "description": "Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages.",
 "type": "boolean"
@@ -1487,6 +1491,13 @@
 "common": {
 "$ref": "CommonLanguageSettings",
 "description": "Some settings."
+},
+"renamedServices": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Map of service names to renamed services. Keys are the package relative service names and values are the name to be used for the service client and call options. publishing: go_settings: renamed_services: Publisher: TopicAdmin",
+"type": "object"
 }
 },
 "type": "object"
@@ -2427,7 +2438,7 @@
 "type": "string"
 },
 "unit": {
-"description": "Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
+"description": "Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
 "type": "string"
 },
 "values": {

googleapiclient/discovery_cache/documents/serviceconsumermanagement.v1beta1.json

@@ -715,7 +715,7 @@
 }
 }
 },
-"revision": "20240929",
+"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"
@@ -1433,6 +1437,10 @@
 "description": "Experimental features to be included during client library generation. These fields will be deprecated once the feature graduates and is enabled by default.",
 "id": "ExperimentalFeatures",
 "properties": {
+"protobufPythonicTypesEnabled": {
+"description": "Enables generation of protobuf code using new types that are more Pythonic which are included in `protobuf>=5.29.x`. This feature will be enabled by default 1 month after launching the feature in preview packages.",
+"type": "boolean"
+},
 "restAsyncIoEnabled": {
 "description": "Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages.",
 "type": "boolean"
@@ -1572,6 +1580,13 @@
 "common": {
 "$ref": "CommonLanguageSettings",
 "description": "Some settings."
+},
+"renamedServices": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Map of service names to renamed services. Keys are the package relative service names and values are the name to be used for the service client and call options. publishing: go_settings: renamed_services: Publisher: TopicAdmin",
+"type": "object"
 }
 },
 "type": "object"
@@ -2458,7 +2473,7 @@
 "type": "string"
 },
 "unit": {
-"description": "Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
+"description": "Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
 "type": "string"
 },
 "values": {
@@ -3012,13 +3027,17 @@
 "id": "V1Beta1ImportProducerQuotaPoliciesRequest",
 "properties": {
 "force": {
-"description": "Whether to force the import of the quota policies. If the policy import would decrease the default limit of any consumer tier by more than 10 percent, the call is rejected, as a safety measure to avoid accidentally decreasing quota too quickly. Setting the force parameter to true ignores this restriction.",
+"description": "Whether quota policy can result in a decrease of effective limit. Don't allow any decreases if force is not specified. If force is specified, then don't allow any decreases below 120% of the 7d quota usage, or for cases where usage cannot be examined (custom dimensions/ per user/per resource), only allow a 10% decrease.",
 "type": "boolean"
 },
 "forceJustification": {
-"description": "If force option is set to true, force_justification is suggested to be set to log the reason in audit logs.",
+"description": "If force or force_skip_quota_usage_check option is set to true, force_justification is suggested to be set to log the reason in audit logs.",
 "type": "string"
 },
+"forceSkipQuotaUsageCheck": {
+"description": "If set to true, skip the quota usage check. This field is only used when the effective limit can be decreased. If the force field is not set, this field will be ignored.",
+"type": "boolean"
+},
 "inlineSource": {
 "$ref": "V1Beta1PolicyInlineSource",
 "description": "The import data is specified in the request message itself"

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/servicemanagement.v1.json

@@ -830,7 +830,7 @@
 }
 }
 },
-"revision": "20241106",
+"revision": "20241202",
 "rootUrl": "https://servicemanagement.googleapis.com/",
 "schemas": {
 "Advice": {
@@ -1568,6 +1568,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"
@@ -2039,6 +2043,13 @@
 "common": {
 "$ref": "CommonLanguageSettings",
 "description": "Some settings."
+},
+"renamedServices": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Map of service names to renamed services. Keys are the package relative service names and values are the name to be used for the service client and call options. publishing: go_settings: renamed_services: Publisher: TopicAdmin",
+"type": "object"
 }
 },
 "type": "object"

googleapiclient/discovery_cache/documents/servicenetworking.v1.json

@@ -111,7 +111,7 @@
 "operations": {
 "methods": {
 "cancel": {
-"description": "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`.",
+"description": "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`.",
 "flatPath": "v1/operations/{operationsId}:cancel",
 "httpMethod": "POST",
 "id": "servicenetworking.operations.cancel",
@@ -1029,7 +1029,7 @@
 }
 }
 },
-"revision": "20241113",
+"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

@@ -114,7 +114,7 @@
 "operations": {
 "methods": {
 "cancel": {
-"description": "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`.",
+"description": "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`.",
 "flatPath": "v1/operations/{operationsId}:cancel",
 "httpMethod": "POST",
 "id": "serviceusage.operations.cancel",
@@ -426,7 +426,7 @@
 }
 }
 },
-"revision": "20241025",
+"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"
@@ -1524,6 +1528,10 @@
 "description": "Experimental features to be included during client library generation. These fields will be deprecated once the feature graduates and is enabled by default.",
 "id": "ExperimentalFeatures",
 "properties": {
+"protobufPythonicTypesEnabled": {
+"description": "Enables generation of protobuf code using new types that are more Pythonic which are included in `protobuf>=5.29.x`. This feature will be enabled by default 1 month after launching the feature in preview packages.",
+"type": "boolean"
+},
 "restAsyncIoEnabled": {
 "description": "Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages.",
 "type": "boolean"
@@ -1692,6 +1700,13 @@
 "common": {
 "$ref": "CommonLanguageSettings",
 "description": "Some settings."
+},
+"renamedServices": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Map of service names to renamed services. Keys are the package relative service names and values are the name to be used for the service client and call options. publishing: go_settings: renamed_services: Publisher: TopicAdmin",
+"type": "object"
 }
 },
 "type": "object"
@@ -3226,7 +3241,7 @@
 "type": "string"
 },
 "unit": {
-"description": "Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
+"description": "Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
 "type": "string"
 },
 "values": {

googleapiclient/discovery_cache/documents/serviceusage.v1beta1.json

@@ -964,7 +964,7 @@
 }
 }
 },
-"revision": "20241025",
+"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"
@@ -2101,6 +2105,10 @@
 "description": "Experimental features to be included during client library generation. These fields will be deprecated once the feature graduates and is enabled by default.",
 "id": "ExperimentalFeatures",
 "properties": {
+"protobufPythonicTypesEnabled": {
+"description": "Enables generation of protobuf code using new types that are more Pythonic which are included in `protobuf>=5.29.x`. This feature will be enabled by default 1 month after launching the feature in preview packages.",
+"type": "boolean"
+},
 "restAsyncIoEnabled": {
 "description": "Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages.",
 "type": "boolean"
@@ -2269,6 +2277,13 @@
 "common": {
 "$ref": "CommonLanguageSettings",
 "description": "Some settings."
+},
+"renamedServices": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Map of service names to renamed services. Keys are the package relative service names and values are the name to be used for the service client and call options. publishing: go_settings: renamed_services: Publisher: TopicAdmin",
+"type": "object"
 }
 },
 "type": "object"
@@ -4014,7 +4029,7 @@
 "type": "string"
 },
 "unit": {
-"description": "Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
+"description": "Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
 "type": "string"
 },
 "values": {

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/spanner.v1.json

@@ -2806,7 +2806,7 @@
 "type": "string"
 },
 "instancePartitionDeadline": {
-"description": "Optional. Deadline used while retrieving metadata for instance partition operations. Instance partitions whose operation metadata cannot be retrieved within this deadline will be added to unreachable in ListInstancePartitionOperationsResponse.",
+"description": "Optional. Deadline used while retrieving metadata for instance partition operations. Instance partitions whose operation metadata cannot be retrieved within this deadline will be added to unreachable_instance_partitions in ListInstancePartitionOperationsResponse.",
 "format": "google-datetime",
 "location": "query",
 "type": "string"
@@ -3319,7 +3319,7 @@
 }
 }
 },
-"revision": "20241020",
+"revision": "20241119",
 "rootUrl": "https://spanner.googleapis.com/",
 "schemas": {
 "AsymmetricAutoscalingOption": {
@@ -3578,7 +3578,7 @@
 "type": "object"
 },
 "BackupSchedule": {
-"description": "BackupSchedule expresses the automated backup creation specification for a Spanner database. Next ID: 10",
+"description": "BackupSchedule expresses the automated backup creation specification for a Spanner database.",
 "id": "BackupSchedule",
 "properties": {
 "encryptionConfig": {
@@ -4126,7 +4126,7 @@
 "type": "object"
 },
 "CreateInstanceConfigRequest": {
-"description": "The request for CreateInstanceConfigRequest.",
+"description": "The request for CreateInstanceConfig.",
 "id": "CreateInstanceConfigRequest",
 "properties": {
 "instanceConfig": {
@@ -4912,7 +4912,7 @@
 "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."
+"A default backup schedule will be created automatically on creation of a database within the instance. Once created, the default backup schedule can be edited or deleted just like any other backup schedule. Currently, the default backup schedule creates a full backup every 24 hours and retains the backup for a period of 7 days."
 ],
 "type": "string"
 },
@@ -7240,7 +7240,7 @@
 "type": "object"
 },
 "UpdateInstanceConfigRequest": {
-"description": "The request for UpdateInstanceConfigRequest.",
+"description": "The request for UpdateInstanceConfig.",
 "id": "UpdateInstanceConfigRequest",
 "properties": {
 "instanceConfig": {