google-api-python-client 2.91.0__py2.py3-none-any.whl → 2.93.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/gkeonprem.v1.json

@@ -2996,7 +2996,7 @@
       }
     }
   },
-  "revision": "20230620",
+  "revision": "20230626",
   "rootUrl": "https://gkeonprem.googleapis.com/",
   "schemas": {
     "Authorization": {
@@ -4733,6 +4733,63 @@
       },
       "type": "object"
     },
+    "Metric": {
+      "description": "Progress metric is (string, int|float|string) pair.",
+      "id": "Metric",
+      "properties": {
+        "doubleValue": {
+          "description": "For metrics with floating point value.",
+          "format": "double",
+          "type": "number"
+        },
+        "intValue": {
+          "description": "For metrics with integer value.",
+          "format": "int64",
+          "type": "string"
+        },
+        "metric": {
+          "description": "Required. The metric name.",
+          "enum": [
+            "METRIC_ID_UNSPECIFIED",
+            "NODES_TOTAL",
+            "NODES_DRAINING",
+            "NODES_UPGRADING",
+            "NODES_PENDING_UPGRADE",
+            "NODES_UPGRADED",
+            "NODES_FAILED",
+            "NODES_HEALTHY",
+            "NODES_RECONCILING",
+            "NODES_IN_MAINTENANCE",
+            "PREFLIGHTS_COMPLETED",
+            "PREFLIGHTS_RUNNING",
+            "PREFLIGHTS_FAILED",
+            "PREFLIGHTS_TOTAL"
+          ],
+          "enumDescriptions": [
+            "Not set.",
+            "The total number of nodes being actuated.",
+            "The number of nodes draining.",
+            "The number of nodes actively upgrading.",
+            "The number of nodes to be upgraded.",
+            "The number of nodes upgraded.",
+            "The number of nodes to fail actuation.",
+            "The number of nodes healthy.",
+            "The number of nodes reconciling.",
+            "The number of nodes in maintenance mode.",
+            "The number of completed preflight checks.",
+            "The number of preflight checks running.",
+            "The number of preflight checks failed.",
+            "The total number of preflight checks."
+          ],
+          "type": "string"
+        },
+        "stringValue": {
+          "description": "For metrics with custom values (ratios, visual progress, etc.).",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "NodeTaint": {
       "description": "NodeTaint applied to every Kubernetes node in a node pool. Kubernetes taints can be used together with tolerations to control how workloads are scheduled to your nodes. Node taints are permanent.",
       "id": "NodeTaint",
@@ -4825,6 +4882,11 @@
           "readOnly": true,
           "type": "string"
         },
+        "progress": {
+          "$ref": "OperationProgress",
+          "description": "Output only. Detailed progress information for the operation.",
+          "readOnly": true
+        },
         "requestedCancellation": {
           "description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have successfully been cancelled have [Operation.error] value with a [google.rpc.Status.code] of 1, corresponding to `Code.CANCELLED`.",
           "readOnly": true,
@@ -4867,6 +4929,83 @@
       },
       "type": "object"
     },
+    "OperationProgress": {
+      "description": "Information about operation progress. LINT.IfChange",
+      "id": "OperationProgress",
+      "properties": {
+        "stages": {
+          "description": "The stages of the operation.",
+          "items": {
+            "$ref": "OperationStage"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "OperationStage": {
+      "description": "Information about a particular stage of an operation.",
+      "id": "OperationStage",
+      "properties": {
+        "endTime": {
+          "description": "Time the stage ended.",
+          "format": "google-datetime",
+          "type": "string"
+        },
+        "metrics": {
+          "description": "Progress metric bundle.",
+          "items": {
+            "$ref": "Metric"
+          },
+          "type": "array"
+        },
+        "stage": {
+          "description": "The high-level stage of the operation.",
+          "enum": [
+            "STAGE_UNSPECIFIED",
+            "PREFLIGHT_CHECK",
+            "CONFIGURE",
+            "DEPLOY",
+            "HEALTH_CHECK",
+            "UPDATE"
+          ],
+          "enumDescriptions": [
+            "Not set.",
+            "Preflight checks are running.",
+            "Resource is being configured.",
+            "Resource is being deployed.",
+            "Waiting for the resource to become healthy.",
+            "Resource is being updated."
+          ],
+          "type": "string"
+        },
+        "startTime": {
+          "description": "Time the stage started.",
+          "format": "google-datetime",
+          "type": "string"
+        },
+        "state": {
+          "description": "Output only. State of the stage.",
+          "enum": [
+            "STATE_UNSPECIFIED",
+            "PENDING",
+            "RUNNING",
+            "SUCCEEDED",
+            "FAILED"
+          ],
+          "enumDescriptions": [
+            "Not set.",
+            "The stage is pending.",
+            "The stage is running",
+            "The stage has completed successfully.",
+            "The stage has failed."
+          ],
+          "readOnly": true,
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "Policy": {
       "description": "An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources. A `Policy` is a collection of `bindings`. A `binding` binds one or more `members`, or principals, to a single `role`. Principals can be user accounts, service accounts, Google groups, and domains (such as G Suite). A `role` is a named list of permissions; each `role` can be an IAM predefined role or a user-created custom role. For some types of Google Cloud resources, a `binding` can also specify a `condition`, which is a logical expression that allows access to a resource only if the expression evaluates to `true`. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies). **JSON example:** { \"bindings\": [ { \"role\": \"roles/resourcemanager.organizationAdmin\", \"members\": [ \"user:mike@example.com\", \"group:admins@example.com\", \"domain:google.com\", \"serviceAccount:my-project-id@appspot.gserviceaccount.com\" ] }, { \"role\": \"roles/resourcemanager.organizationViewer\", \"members\": [ \"user:eve@example.com\" ], \"condition\": { \"title\": \"expirable access\", \"description\": \"Does not grant access after Sep 2020\", \"expression\": \"request.time < timestamp('2020-10-01T00:00:00.000Z')\", } } ], \"etag\": \"BwWWja0YfJA=\", \"version\": 3 } **YAML example:** bindings: - members: - user:mike@example.com - group:admins@example.com - domain:google.com - serviceAccount:my-project-id@appspot.gserviceaccount.com role: roles/resourcemanager.organizationAdmin - members: - user:eve@example.com role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time < timestamp('2020-10-01T00:00:00.000Z') etag: BwWWja0YfJA= version: 3 For a description of IAM and its features, see the [IAM documentation](https://cloud.google.com/iam/docs/).",
       "id": "Policy",

googleapiclient/discovery_cache/documents/gmail.v1.json

@@ -3077,7 +3077,7 @@
       }
     }
   },
-  "revision": "20230619",
+  "revision": "20230703",
   "rootUrl": "https://gmail.googleapis.com/",
   "schemas": {
     "AutoForwarding": {
@@ -4348,7 +4348,8 @@
       "id": "WatchRequest",
       "properties": {
         "labelFilterAction": {
-          "description": "Filtering behavior of labelIds list specified.",
+          "deprecated": true,
+          "description": "Filtering behavior of `labelIds list` specified. This field is deprecated because it caused incorrect behavior in some cases; use `label_filter_behavior` instead.",
           "enum": [
             "include",
             "exclude"
@@ -4360,7 +4361,7 @@
           "type": "string"
         },
         "labelFilterBehavior": {
-          "description": "Filtering behavior of labelIds list specified. This field replaces label_filter_action; if set, label_filter_action is ignored.",
+          "description": "Filtering behavior of `labelIds list` specified. This field replaces `label_filter_action`; if set, `label_filter_action` is ignored.",
           "enum": [
             "include",
             "exclude"

googleapiclient/discovery_cache/documents/gmailpostmastertools.v1.json

@@ -265,7 +265,7 @@
       }
     }
   },
-  "revision": "20230625",
+  "revision": "20230708",
   "rootUrl": "https://gmailpostmastertools.googleapis.com/",
   "schemas": {
     "DeliveryError": {

googleapiclient/discovery_cache/documents/gmailpostmastertools.v1beta1.json

@@ -265,7 +265,7 @@
       }
     }
   },
-  "revision": "20230625",
+  "revision": "20230708",
   "rootUrl": "https://gmailpostmastertools.googleapis.com/",
   "schemas": {
     "DeliveryError": {
@@ -382,6 +382,7 @@
           "type": "string"
         },
         "numIps": {
+          "deprecated": true,
           "description": "Total number of unique IPs in this reputation category. This metric only pertains to traffic that passed [SPF](http://www.openspf.org/) or [DKIM](http://www.dkim.org/). Deprecated to be complied with ApiLinter for Quantities. Use ip_count instead.",
           "format": "int64",
           "type": "string"

googleapiclient/discovery_cache/documents/groupsmigration.v1.json

@@ -146,7 +146,7 @@
       }
     }
   },
-  "revision": "20230302",
+  "revision": "20230626",
   "rootUrl": "https://groupsmigration.googleapis.com/",
   "schemas": {
     "Groups": {

googleapiclient/discovery_cache/documents/healthcare.v1.json

@@ -4078,7 +4078,7 @@
       }
     }
   },
-  "revision": "20230616",
+  "revision": "20230627",
   "rootUrl": "https://healthcare.googleapis.com/",
   "schemas": {
     "ActivateConsentRequest": {
@@ -4802,6 +4802,13 @@
         "notificationConfig": {
           "$ref": "NotificationConfig",
           "description": "Notification destination for new DICOM instances. Supplied by the client."
+        },
+        "streamConfigs": {
+          "description": "Optional. A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.",
+          "items": {
+            "$ref": "GoogleCloudHealthcareV1DicomStreamConfig"
+          },
+          "type": "array"
         }
       },
       "type": "object"
@@ -4996,10 +5003,18 @@
           "format": "google-datetime",
           "type": "string"
         },
+        "filter": {
+          "description": "Restricts messages exported to those matching a filter, only applicable to PubsubDestination and GcsDestination. The following syntax is available: * A string field value can be written as text inside quotation marks, for example `\"query text\"`. The only valid relational operation for text fields is equality (`=`), where text is searched within the field, rather than having the field be equal to the text. For example, `\"Comment = great\"` returns messages with `great` in the comment field. * A number field value can be written as an integer, a decimal, or an exponential. The valid relational operators for number fields are the equality operator (`=`), along with the less than/greater than operators (`<`, `<=`, `>`, `>=`). Note that there is no inequality (`!=`) operator. You can prepend the `NOT` operator to an expression to negate it. * A date field value must be written in the `yyyy-mm-dd` format. Fields with date and time use the RFC3339 time format. Leading zeros are required for one-digit months and days. The valid relational operators for date fields are the equality operator (`=`) , along with the less than/greater than operators (`<`, `<=`, `>`, `>=`). Note that there is no inequality (`!=`) operator. You can prepend the `NOT` operator to an expression to negate it. * Multiple field query expressions can be combined in one query by adding `AND` or `OR` operators between the expressions. If a boolean operator appears within a quoted string, it is not treated as special, and is just another part of the character string to be matched. You can prepend the `NOT` operator to an expression to negate it. The following fields and functions are available for filtering: * `message_type`, from the MSH-9.1 field. For example, `NOT message_type = \"ADT\"`. * `send_date` or `sendDate`, the `yyyy-mm-dd` date the message was sent in the dataset's time_zone, from the MSH-7 segment. For example, `send_date < \"2017-01-02\"`. * `send_time`, the timestamp when the message was sent, using the RFC3339 time format for comparisons, from the MSH-7 segment. For example, `send_time < \"2017-01-02T00:00:00-05:00\"`. * `create_time`, the timestamp when the message was created in the HL7v2 store. Use the RFC3339 time format for comparisons. For example, `create_time < \"2017-01-02T00:00:00-05:00\"`. * `send_facility`, the care center that the message came from, from the MSH-4 segment. For example, `send_facility = \"ABC\"`. Note: The filter will be applied to every message in the HL7v2 store whose `send_time` lies in the range defined by the `start_time` and the `end_time`. Even if the filter only matches a small set of messages, the export operation can still take a long time to finish when a lot of messages are between the specified `start_time` and `end_time` range.",
+          "type": "string"
+        },
         "gcsDestination": {
           "$ref": "GcsDestination",
           "description": "Export to a Cloud Storage destination."
         },
+        "pubsubDestination": {
+          "$ref": "PubsubDestination",
+          "description": "Export messages to a Pub/Sub topic."
+        },
         "startTime": {
           "description": "The start of the range in `send_time` (MSH.7, https://www.hl7.org/documentcenter/public_temp_2E58C1F9-1C23-BA17-0C6126475344DA9D/wg/conf/HL7MSH.htm) to process. If not specified, the UNIX epoch (1970-01-01T00:00:00Z) is used. This value has to come before the `end_time` defined below. Only messages whose `send_time` lies in the range `start_time` (inclusive) to `end_time` (exclusive) are exported.",
           "format": "google-datetime",
@@ -5466,6 +5481,17 @@
       },
       "type": "object"
     },
+    "GoogleCloudHealthcareV1DicomStreamConfig": {
+      "description": "StreamConfig specifies configuration for a streaming DICOM export.",
+      "id": "GoogleCloudHealthcareV1DicomStreamConfig",
+      "properties": {
+        "bigqueryDestination": {
+          "$ref": "GoogleCloudHealthcareV1DicomBigQueryDestination",
+          "description": "Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: `service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com`. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging))."
+        }
+      },
+      "type": "object"
+    },
     "GoogleCloudHealthcareV1FhirBigQueryDestination": {
       "description": "The configuration for exporting to BigQuery.",
       "id": "GoogleCloudHealthcareV1FhirBigQueryDestination",
@@ -6176,6 +6202,10 @@
         "pubsubTopic": {
           "description": "The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging)). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see [Configuring Pub/Sub notifications](https://cloud.google.com/healthcare/docs/how-tos/pubsub) for specific details.",
           "type": "string"
+        },
+        "sendForBulkImport": {
+          "description": "Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.",
+          "type": "boolean"
         }
       },
       "type": "object"
@@ -6364,6 +6394,17 @@
       },
       "type": "object"
     },
+    "PubsubDestination": {
+      "description": "The Pub/Sub output destination. The Cloud Healthcare Service Agent requires the `roles/pubsub.publisher` Cloud IAM role on the Pub/Sub topic.",
+      "id": "PubsubDestination",
+      "properties": {
+        "pubsubTopic": {
+          "description": "The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that Pub/Sub messages are published on. Supplied by the client. The `PubsubMessage` contains the following fields: * `PubsubMessage.Data` contains the resource name. * `PubsubMessage.MessageId` is the ID of this notification. It is guaranteed to be unique within the topic. * `PubsubMessage.PublishTime` is the time when the message was published. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "QueryAccessibleDataRequest": {
       "description": "Queries all data_ids that are consented for a given use in the given consent store and writes them to a specified destination. The returned Operation includes a progress counter for the number of User data mappings processed. Errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging] (https://cloud.google.com/healthcare/docs/how-tos/logging) and [QueryAccessibleData] for a sample log entry).",
       "id": "QueryAccessibleDataRequest",

googleapiclient/discovery_cache/documents/healthcare.v1beta1.json

@@ -4941,7 +4941,7 @@
       }
     }
   },
-  "revision": "20230616",
+  "revision": "20230627",
   "rootUrl": "https://healthcare.googleapis.com/",
   "schemas": {
     "Action": {
@@ -5940,7 +5940,7 @@
           "description": "Notification destination for new DICOM instances. Supplied by the client."
         },
         "streamConfigs": {
-          "description": "A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.",
+          "description": "Optional. A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.",
           "items": {
             "$ref": "GoogleCloudHealthcareV1beta1DicomStreamConfig"
           },
@@ -6245,10 +6245,18 @@
           "format": "google-datetime",
           "type": "string"
         },
+        "filter": {
+          "description": "Restricts messages exported to those matching a filter, only applicable to PubsubDestination and GcsDestination. The following syntax is available: * A string field value can be written as text inside quotation marks, for example `\"query text\"`. The only valid relational operation for text fields is equality (`=`), where text is searched within the field, rather than having the field be equal to the text. For example, `\"Comment = great\"` returns messages with `great` in the comment field. * A number field value can be written as an integer, a decimal, or an exponential. The valid relational operators for number fields are the equality operator (`=`), along with the less than/greater than operators (`<`, `<=`, `>`, `>=`). Note that there is no inequality (`!=`) operator. You can prepend the `NOT` operator to an expression to negate it. * A date field value must be written in the `yyyy-mm-dd` format. Fields with date and time use the RFC3339 time format. Leading zeros are required for one-digit months and days. The valid relational operators for date fields are the equality operator (`=`) , along with the less than/greater than operators (`<`, `<=`, `>`, `>=`). Note that there is no inequality (`!=`) operator. You can prepend the `NOT` operator to an expression to negate it. * Multiple field query expressions can be combined in one query by adding `AND` or `OR` operators between the expressions. If a boolean operator appears within a quoted string, it is not treated as special, and is just another part of the character string to be matched. You can prepend the `NOT` operator to an expression to negate it. The following fields and functions are available for filtering: * `message_type`, from the MSH-9.1 field. For example, `NOT message_type = \"ADT\"`. * `send_date` or `sendDate`, the YYYY-MM-DD date the message was sent in the dataset's time_zone, from the MSH-7 segment. For example, `send_date < \"2017-01-02\"`. * `send_time`, the timestamp when the message was sent, using the RFC3339 time format for comparisons, from the MSH-7 segment. For example, `send_time < \"2017-01-02T00:00:00-05:00\"`. * `create_time`, the timestamp when the message was created in the HL7v2 store. Use the RFC3339 time format for comparisons. For example, `create_time < \"2017-01-02T00:00:00-05:00\"`. * `send_facility`, the care center that the message came from, from the MSH-4 segment. For example, `send_facility = \"ABC\"`. Note: The filter will be applied to every message in the HL7v2 store whose `send_time` lies in the range defined by the `start_time` and the `end_time`. Even if the filter only matches a small set of messages, the export operation can still take a long time to finish when a lot of messages are between the specified `start_time` and `end_time` range.",
+          "type": "string"
+        },
         "gcsDestination": {
           "$ref": "GcsDestination",
           "description": "Export to a Cloud Storage destination."
         },
+        "pubsubDestination": {
+          "$ref": "PubsubDestination",
+          "description": "Export messages to a Pub/Sub topic."
+        },
         "startTime": {
           "description": "The start of the range in `send_time` (MSH.7, https://www.hl7.org/documentcenter/public_temp_2E58C1F9-1C23-BA17-0C6126475344DA9D/wg/conf/HL7MSH.htm) to process. If not specified, the UNIX epoch (1970-01-01T00:00:00Z) is used. This value has to come before the `end_time` defined below. Only messages whose `send_time` lies in the range `start_time` (inclusive) to `end_time` (exclusive) are exported.",
           "format": "google-datetime",
@@ -8000,6 +8008,17 @@
       },
       "type": "object"
     },
+    "PubsubDestination": {
+      "description": "The Pub/Sub output destination. The Cloud Healthcare Service Agent requires the `roles/pubsub.publisher` Cloud IAM role on the Pub/Sub topic.",
+      "id": "PubsubDestination",
+      "properties": {
+        "pubsubTopic": {
+          "description": "The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that Pub/Sub messages are published on. Supplied by the client. The `PubsubMessage` contains the following fields: * `PubsubMessage.Data` contains the resource name. * `PubsubMessage.MessageId` is the ID of this notification. It is guaranteed to be unique within the topic. * `PubsubMessage.PublishTime` is the time when the message was published. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "QueryAccessibleDataRequest": {
       "description": "Queries all data_ids that are consented for a given use in the given consent store and writes them to a specified destination. The returned Operation includes a progress counter for the number of User data mappings processed. Errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging] (https://cloud.google.com/healthcare/docs/how-tos/logging) and [QueryAccessibleData] for a sample log entry).",
       "id": "QueryAccessibleDataRequest",

googleapiclient/discovery_cache/documents/homegraph.v1.json

@@ -216,7 +216,7 @@
       }
     }
   },
-  "revision": "20230526",
+  "revision": "20230623",
   "rootUrl": "https://homegraph.googleapis.com/",
   "schemas": {
     "AgentDeviceId": {