google-api-python-client 2.171.0__py3-none-any.whl → 2.173.0__py3-none-any.whl

googleapiclient/discovery_cache/documents/cloudresourcemanager.v3.json

@@ -697,11 +697,11 @@
 "https://www.googleapis.com/auth/cloud-platform.read-only"
 ]
 },
-"patch": {
-"description": "Updates tag bindings directly attached to a GCP resource. Update_mask can be kept empty or \"*\".",
+"update": {
+"description": "Updates tag bindings directly attached to a GCP resource.",
 "flatPath": "v3/locations/{locationsId}/tagBindingCollections/{tagBindingCollectionsId}",
-"httpMethod": "PATCH",
-"id": "cloudresourcemanager.locations.tagBindingCollections.patch",
+"httpMethod": "PUT",
+"id": "cloudresourcemanager.locations.tagBindingCollections.update",
 "parameterOrder": [
 "name"
 ],
@@ -712,12 +712,6 @@
 "pattern": "^locations/[^/]+/tagBindingCollections/[^/]+$",
 "required": true,
 "type": "string"
-},
-"updateMask": {
-"description": "Optional. An update mask to selectively update fields.",
-"format": "google-fieldmask",
-"location": "query",
-"type": "string"
 }
 },
 "path": "v3/{+name}",
@@ -1968,7 +1962,7 @@
 }
 }
 },
-"revision": "20250522",
+"revision": "20250606",
 "rootUrl": "https://cloudresourcemanager.googleapis.com/",
 "schemas": {
 "AuditConfig": {
@@ -2816,6 +2810,14 @@
 "description": "A project is a high-level Google Cloud entity. It is a container for ACLs, APIs, App Engine Apps, VMs, and other Google Cloud Platform resources.",
 "id": "Project",
 "properties": {
+"configuredCapabilities": {
+"description": "Output only. If this project is a Management Project, list of capabilities configured on the parent folder. Note, presence of any capability implies that this is a Management Project. Example: `folders/123/capabilities/app-management`. OUTPUT ONLY.",
+"items": {
+"type": "string"
+},
+"readOnly": true,
+"type": "array"
+},
 "createTime": {
 "description": "Output only. Creation time.",
 "format": "google-datetime",

googleapiclient/discovery_cache/documents/cloudscheduler.v1.json

@@ -535,7 +535,7 @@
 }
 }
 },
-"revision": "20250411",
+"revision": "20250530",
 "rootUrl": "https://cloudscheduler.googleapis.com/",
 "schemas": {
 "AppEngineHttpTarget": {
@@ -718,6 +718,11 @@
 "$ref": "RetryConfig",
 "description": "Settings that determine the retry behavior."
 },
+"satisfiesPzs": {
+"description": "Output only. Whether or not this Job satisfies the requirements of physical zone separation",
+"readOnly": true,
+"type": "boolean"
+},
 "schedule": {
 "description": "Required, except when used with UpdateJob. Describes the schedule on which the job will be executed. The schedule can be either of the following types: * [Crontab](https://en.wikipedia.org/wiki/Cron#Overview) * English-like [schedule](https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules) As a general rule, execution `n + 1` of a job will not begin until execution `n` has finished. Cloud Scheduler will never allow two simultaneously outstanding executions. For example, this implies that if the `n+1`th execution is scheduled to run at 16:00 but the `n`th execution takes until 16:15, the `n+1`th execution will not start until `16:15`. A scheduled start time will be delayed if the previous execution has not ended when its scheduled time occurs. If retry_count > 0 and a job attempt fails, the job will be tried a total of retry_count times, with exponential backoff, until the next scheduled start time. If retry_count is 0, a job attempt will not be retried if it fails. Instead the Cloud Scheduler system will wait for the next scheduled execution time. Setting retry_count to 0 does not prevent failed jobs from running according to schedule after the failure.",
 "type": "string"
@@ -1030,7 +1035,7 @@
 "type": "object"
 },
 "RetryConfig": {
-"description": "Settings that determine the retry behavior. By default, if a job does not complete successfully (meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings in RetryConfig.",
+"description": "Settings that determine the retry behavior. For more information, see [Retry jobs](https://cloud.google.com/scheduler/docs/configuring/retry-jobs). By default, if a job does not complete successfully (meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings in RetryConfig.",
 "id": "RetryConfig",
 "properties": {
 "maxBackoffDuration": {
@@ -1039,12 +1044,12 @@
 "type": "string"
 },
 "maxDoublings": {
-"description": "The time between retries will double `max_doublings` times. A job's retry interval starts at min_backoff_duration, then doubles `max_doublings` times, then increases linearly, and finally retries at intervals of max_backoff_duration up to retry_count times. For example, if min_backoff_duration is 10s, max_backoff_duration is 300s, and `max_doublings` is 3, then the job will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the job will retry at intervals of max_backoff_duration until the job has been attempted retry_count times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... The default value of this field is 5.",
+"description": "The time between retries will double `max_doublings` times. A job's retry interval starts at min_backoff_duration, then doubles `max_doublings` times, then increases linearly, and finally retries at intervals of max_backoff_duration up to retry_count times. For examples, see [Retry jobs](https://cloud.google.com/scheduler/docs/configuring/retry-jobs#max-doublings). The default value of this field is 5.",
 "format": "int32",
 "type": "integer"
 },
 "maxRetryDuration": {
-"description": "The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retry_count, the job will be retried until both limits are reached. The default value for max_retry_duration is zero, which means retry duration is unlimited.",
+"description": "The time limit for retrying a failed job, measured from the time when an execution was first attempted. If specified with retry_count, the job will be retried until both limits are reached. The default value for max_retry_duration is zero, which means retry duration is unlimited. However, if retry_count is also 0, a job attempt won't be retried if it fails.",
 "format": "google-duration",
 "type": "string"
 },
@@ -1054,7 +1059,7 @@
 "type": "string"
 },
 "retryCount": {
-"description": "The number of attempts that the system will make to run a job using the exponential backoff procedure described by max_doublings. The default value of retry_count is zero. If retry_count is 0, a job attempt will not be retried if it fails. Instead the Cloud Scheduler system will wait for the next scheduled execution time. Setting retry_count to 0 does not prevent failed jobs from running according to schedule after the failure. If retry_count is set to a non-zero number then Cloud Scheduler will retry failed attempts, using exponential backoff, retry_count times, or until the next scheduled execution time, whichever comes first. Values greater than 5 and negative values are not allowed.",
+"description": "The number of attempts that the system will make to run a job using the exponential backoff procedure described by max_doublings. The default value of retry_count is zero. If retry_count is 0 (and if max_retry_duration is also 0), a job attempt won't be retried if it fails. Instead, Cloud Scheduler system will wait for the next scheduled execution time. Setting retry_count to 0 doesn't prevent failed jobs from running according to schedule after the failure. If retry_count is set to a non-zero number, Cloud Scheduler will retry the failed job, using exponential backoff, for retry_count times until the job succeeds or the number of retries is exhausted. Note that the next scheduled execution time might be skipped if the retries continue through that time. Values greater than 5 and negative values are not allowed.",
 "format": "int32",
 "type": "integer"
 }

googleapiclient/discovery_cache/documents/cloudscheduler.v1beta1.json

@@ -439,7 +439,7 @@
 }
 }
 },
-"revision": "20250411",
+"revision": "20250530",
 "rootUrl": "https://cloudscheduler.googleapis.com/",
 "schemas": {
 "AppEngineHttpTarget": {
@@ -620,6 +620,11 @@
 "$ref": "RetryConfig",
 "description": "Settings that determine the retry behavior."
 },
+"satisfiesPzs": {
+"description": "Output only. Whether or not this Job satisfies the requirements of physical zone separation",
+"readOnly": true,
+"type": "boolean"
+},
 "schedule": {
 "description": "Required, except when used with UpdateJob. Describes the schedule on which the job will be executed. The schedule can be either of the following types: * [Crontab](https://en.wikipedia.org/wiki/Cron#Overview) * English-like [schedule](https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules) As a general rule, execution `n + 1` of a job will not begin until execution `n` has finished. Cloud Scheduler will never allow two simultaneously outstanding executions. For example, this implies that if the `n+1`th execution is scheduled to run at 16:00 but the `n`th execution takes until 16:15, the `n+1`th execution will not start until `16:15`. A scheduled start time will be delayed if the previous execution has not ended when its scheduled time occurs. If retry_count > 0 and a job attempt fails, the job will be tried a total of retry_count times, with exponential backoff, until the next scheduled start time. If retry_count is 0, a job attempt will not be retried if it fails. Instead the Cloud Scheduler system will wait for the next scheduled execution time. Setting retry_count to 0 does not prevent failed jobs from running according to schedule after the failure.",
 "type": "string"
@@ -879,7 +884,7 @@
 "type": "object"
 },
 "RetryConfig": {
-"description": "Settings that determine the retry behavior. By default, if a job does not complete successfully (meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings in RetryConfig.",
+"description": "Settings that determine the retry behavior. For more information, see [Retry jobs](https://cloud.google.com/scheduler/docs/configuring/retry-jobs). By default, if a job does not complete successfully (meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings in RetryConfig.",
 "id": "RetryConfig",
 "properties": {
 "maxBackoffDuration": {
@@ -888,12 +893,12 @@
 "type": "string"
 },
 "maxDoublings": {
-"description": "The time between retries will double `max_doublings` times. A job's retry interval starts at min_backoff_duration, then doubles `max_doublings` times, then increases linearly, and finally retries at intervals of max_backoff_duration up to retry_count times. For example, if min_backoff_duration is 10s, max_backoff_duration is 300s, and `max_doublings` is 3, then the job will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the job will retry at intervals of max_backoff_duration until the job has been attempted retry_count times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... The default value of this field is 5.",
+"description": "The time between retries will double `max_doublings` times. A job's retry interval starts at min_backoff_duration, then doubles `max_doublings` times, then increases linearly, and finally retries at intervals of max_backoff_duration up to retry_count times. For examples, see [Retry jobs](https://cloud.google.com/scheduler/docs/configuring/retry-jobs#max-doublings). The default value of this field is 5.",
 "format": "int32",
 "type": "integer"
 },
 "maxRetryDuration": {
-"description": "The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retry_count, the job will be retried until both limits are reached. The default value for max_retry_duration is zero, which means retry duration is unlimited.",
+"description": "The time limit for retrying a failed job, measured from the time when an execution was first attempted. If specified with retry_count, the job will be retried until both limits are reached. The default value for max_retry_duration is zero, which means retry duration is unlimited. However, if retry_count is also 0, a job attempt won't be retried if it fails.",
 "format": "google-duration",
 "type": "string"
 },
@@ -903,7 +908,7 @@
 "type": "string"
 },
 "retryCount": {
-"description": "The number of attempts that the system will make to run a job using the exponential backoff procedure described by max_doublings. The default value of retry_count is zero. If retry_count is 0, a job attempt will not be retried if it fails. Instead the Cloud Scheduler system will wait for the next scheduled execution time. Setting retry_count to 0 does not prevent failed jobs from running according to schedule after the failure. If retry_count is set to a non-zero number then Cloud Scheduler will retry failed attempts, using exponential backoff, retry_count times, or until the next scheduled execution time, whichever comes first. Values greater than 5 and negative values are not allowed.",
+"description": "The number of attempts that the system will make to run a job using the exponential backoff procedure described by max_doublings. The default value of retry_count is zero. If retry_count is 0 (and if max_retry_duration is also 0), a job attempt won't be retried if it fails. Instead, Cloud Scheduler system will wait for the next scheduled execution time. Setting retry_count to 0 doesn't prevent failed jobs from running according to schedule after the failure. If retry_count is set to a non-zero number, Cloud Scheduler will retry the failed job, using exponential backoff, for retry_count times until the job succeeds or the number of retries is exhausted. Note that the next scheduled execution time might be skipped if the retries continue through that time. Values greater than 5 and negative values are not allowed.",
 "format": "int32",
 "type": "integer"
 }

googleapiclient/discovery_cache/documents/cloudsupport.v2.json

@@ -483,7 +483,7 @@
 "media": {
 "methods": {
 "download": {
-"description": "Download a file attached to a case. Note: HTTP requests must append \"?alt=media\" to the URL. EXAMPLES: cURL: ```shell name=\"projects/some-project/cases/43594844/attachments/0674M00000WijAnZAJ\" curl \\ --header \"Authorization: Bearer $(gcloud auth print-access-token)\" \\ \"https://cloudsupport.googleapis.com/v2/$name:download?alt=media\" ``` Python: ```python import googleapiclient.discovery api_version = \"v2\" supportApiService = googleapiclient.discovery.build( serviceName=\"cloudsupport\", version=api_version, discoveryServiceUrl=f\"https://cloudsupport.googleapis.com/$discovery/rest?version={api_version}\", ) request = supportApiService.media().download( name=\"projects/some-project/cases/43595344/attachments/0684M00000Pw6pHQAR\" ) request.uri = request.uri.split(\"?\")[0] + \"?alt=media\" print(request.execute()) ```",
+"description": "Download a file attached to a case. When this endpoint is called, no \"response body\" will be returned. Instead, the attachment's blob will be returned. Note: HTTP requests must append \"?alt=media\" to the URL. EXAMPLES: cURL: ```shell name=\"projects/some-project/cases/43594844/attachments/0674M00000WijAnZAJ\" curl \\ --header \"Authorization: Bearer $(gcloud auth print-access-token)\" \\ \"https://cloudsupport.googleapis.com/v2/$name:download?alt=media\" ``` Python: ```python import googleapiclient.discovery api_version = \"v2\" supportApiService = googleapiclient.discovery.build( serviceName=\"cloudsupport\", version=api_version, discoveryServiceUrl=f\"https://cloudsupport.googleapis.com/$discovery/rest?version={api_version}\", ) request = supportApiService.media().download( name=\"projects/some-project/cases/43595344/attachments/0684M00000Pw6pHQAR\" ) request.uri = request.uri.split(\"?\")[0] + \"?alt=media\" print(request.execute()) ```",
 "flatPath": "v2/{v2Id}/{v2Id1}/cases/{casesId}/attachments/{attachmentsId}:download",
 "httpMethod": "GET",
 "id": "cloudsupport.media.download",
@@ -552,7 +552,7 @@
 }
 }
 },
-"revision": "20250521",
+"revision": "20250609",
 "rootUrl": "https://cloudsupport.googleapis.com/",
 "schemas": {
 "Actor": {
@@ -1348,47 +1348,6 @@
 }
 },
 "type": "object"
-},
-"WorkflowOperationMetadata": {
-"description": "Metadata about the operation. Used to lookup the current status.",
-"id": "WorkflowOperationMetadata",
-"properties": {
-"namespace": {
-"description": "The namespace that the job was scheduled in. Must be included in the workflow metadata so the workflow status can be retrieved.",
-"type": "string"
-},
-"operationAction": {
-"description": "The type of action the operation is classified as.",
-"enum": [
-"OPERATION_ACTION_UNSPECIFIED",
-"CREATE_SUPPORT_ACCOUNT",
-"UPDATE_SUPPORT_ACCOUNT",
-"PURCHASE_SUPPORT_ACCOUNT"
-],
-"enumDescriptions": [
-"Operation action is not specified.",
-"Operation pertains to the creation of a new support account.",
-"Operation pertains to the updating of an existing support account.",
-"Operation pertains to the purchasing of a support plan that may either create or update a support account."
-],
-"type": "string"
-},
-"workflowOperationType": {
-"description": "Which version of the workflow service this operation came from.",
-"enum": [
-"UNKNOWN_OPERATION_TYPE",
-"WORKFLOWS_V1",
-"WORKFLOWS_V2"
-],
-"enumDescriptions": [
-"Unknown version.",
-"Version 1.",
-"Version 2."
-],
-"type": "string"
-}
-},
-"type": "object"
 }
 },
 "servicePath": "",

googleapiclient/discovery_cache/documents/cloudsupport.v2beta.json

@@ -550,7 +550,7 @@
 "media": {
 "methods": {
 "download": {
-"description": "Download a file attached to a case. Note: HTTP requests must append \"?alt=media\" to the URL. EXAMPLES: cURL: ```shell name=\"projects/some-project/cases/43594844/attachments/0674M00000WijAnZAJ\" curl \\ --header \"Authorization: Bearer $(gcloud auth print-access-token)\" \\ \"https://cloudsupport.googleapis.com/v2/$name:download?alt=media\" ``` Python: ```python import googleapiclient.discovery api_version = \"v2\" supportApiService = googleapiclient.discovery.build( serviceName=\"cloudsupport\", version=api_version, discoveryServiceUrl=f\"https://cloudsupport.googleapis.com/$discovery/rest?version={api_version}\", ) request = supportApiService.media().download( name=\"projects/some-project/cases/43595344/attachments/0684M00000Pw6pHQAR\" ) request.uri = request.uri.split(\"?\")[0] + \"?alt=media\" print(request.execute()) ```",
+"description": "Download a file attached to a case. When this endpoint is called, no \"response body\" will be returned. Instead, the attachment's blob will be returned. Note: HTTP requests must append \"?alt=media\" to the URL. EXAMPLES: cURL: ```shell name=\"projects/some-project/cases/43594844/attachments/0674M00000WijAnZAJ\" curl \\ --header \"Authorization: Bearer $(gcloud auth print-access-token)\" \\ \"https://cloudsupport.googleapis.com/v2/$name:download?alt=media\" ``` Python: ```python import googleapiclient.discovery api_version = \"v2\" supportApiService = googleapiclient.discovery.build( serviceName=\"cloudsupport\", version=api_version, discoveryServiceUrl=f\"https://cloudsupport.googleapis.com/$discovery/rest?version={api_version}\", ) request = supportApiService.media().download( name=\"projects/some-project/cases/43595344/attachments/0684M00000Pw6pHQAR\" ) request.uri = request.uri.split(\"?\")[0] + \"?alt=media\" print(request.execute()) ```",
 "flatPath": "v2beta/{v2betaId}/{v2betaId1}/cases/{casesId}/attachments/{attachmentsId}:download",
 "httpMethod": "GET",
 "id": "cloudsupport.media.download",
@@ -619,7 +619,7 @@
 }
 }
 },
-"revision": "20250521",
+"revision": "20250609",
 "rootUrl": "https://cloudsupport.googleapis.com/",
 "schemas": {
 "Actor": {
@@ -1570,47 +1570,6 @@
 }
 },
 "type": "object"
-},
-"WorkflowOperationMetadata": {
-"description": "Metadata about the operation. Used to lookup the current status.",
-"id": "WorkflowOperationMetadata",
-"properties": {
-"namespace": {
-"description": "The namespace that the job was scheduled in. Must be included in the workflow metadata so the workflow status can be retrieved.",
-"type": "string"
-},
-"operationAction": {
-"description": "The type of action the operation is classified as.",
-"enum": [
-"OPERATION_ACTION_UNSPECIFIED",
-"CREATE_SUPPORT_ACCOUNT",
-"UPDATE_SUPPORT_ACCOUNT",
-"PURCHASE_SUPPORT_ACCOUNT"
-],
-"enumDescriptions": [
-"Operation action is not specified.",
-"Operation pertains to the creation of a new support account.",
-"Operation pertains to the updating of an existing support account.",
-"Operation pertains to the purchasing of a support plan that may either create or update a support account."
-],
-"type": "string"
-},
-"workflowOperationType": {
-"description": "Which version of the workflow service this operation came from.",
-"enum": [
-"UNKNOWN_OPERATION_TYPE",
-"WORKFLOWS_V1",
-"WORKFLOWS_V2"
-],
-"enumDescriptions": [
-"Unknown version.",
-"Version 1.",
-"Version 2."
-],
-"type": "string"
-}
-},
-"type": "object"
 }
 },
 "servicePath": "",

googleapiclient/discovery_cache/documents/cloudtrace.v1.json

@@ -193,7 +193,7 @@
 "type": "string"
 },
 "filter": {
-"description": "Optional. A filter against labels for the request. By default, searches use prefix matching. To specify exact match, prepend a plus symbol (`+`) to the search term. Multiple terms are ANDed. Syntax: * `root:NAME_PREFIX` or `NAME_PREFIX`: Return traces where any root span starts with `NAME_PREFIX`. * `+root:NAME` or `+NAME`: Return traces where any root span's name is exactly `NAME`. * `span:NAME_PREFIX`: Return traces where any span starts with `NAME_PREFIX`. * `+span:NAME`: Return traces where any span's name is exactly `NAME`. * `latency:DURATION`: Return traces whose overall latency is greater or equal to than `DURATION`. Accepted units are nanoseconds (`ns`), milliseconds (`ms`), and seconds (`s`). Default is `ms`. For example, `latency:24ms` returns traces whose overall latency is greater than or equal to 24 milliseconds. * `label:LABEL_KEY`: Return all traces containing the specified label key (exact match, case-sensitive) regardless of the key:value pair's value (including empty values). * `LABEL_KEY:VALUE_PREFIX`: Return all traces containing the specified label key (exact match, case-sensitive) whose value starts with `VALUE_PREFIX`. Both a key and a value must be specified. * `+LABEL_KEY:VALUE`: Return all traces containing a key:value pair exactly matching the specified text. Both a key and a value must be specified. * `method:VALUE`: Equivalent to `/http/method:VALUE`. * `url:VALUE`: Equivalent to `/http/url:VALUE`.",
+"description": "Optional. A filter against properties of the trace. See [filter syntax documentation](https://cloud.google.com/trace/docs/trace-filters) for details.",
 "location": "query",
 "type": "string"
 },
@@ -257,7 +257,7 @@
 }
 }
 },
-"revision": "20250411",
+"revision": "20250530",
 "rootUrl": "https://cloudtrace.googleapis.com/",
 "schemas": {
 "Empty": {