google-api-python-client 2.146.0__py2.py3-none-any.whl → 2.148.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/firebaseml.v2beta.json

@@ -206,7 +206,7 @@
 }
 }
 },
-"revision": "20240911",
+"revision": "20240925",
 "rootUrl": "https://firebaseml.googleapis.com/",
 "schemas": {
 "Date": {
@@ -457,6 +457,30 @@
 },
 "type": "object"
 },
+"GoogleCloudAiplatformV1beta1DynamicRetrievalConfig": {
+"description": "Describes the options to customize dynamic retrieval.",
+"id": "GoogleCloudAiplatformV1beta1DynamicRetrievalConfig",
+"properties": {
+"dynamicThreshold": {
+"description": "Optional. The threshold to be used in dynamic retrieval. If not set, a system default value is used.",
+"format": "float",
+"type": "number"
+},
+"mode": {
+"description": "The mode of the predictor to be used in dynamic retrieval.",
+"enum": [
+"MODE_UNSPECIFIED",
+"MODE_DYNAMIC"
+],
+"enumDescriptions": [
+"Always trigger retrieval.",
+"Run retrieval only when system decides it is necessary."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "GoogleCloudAiplatformV1beta1FileData": {
 "description": "URI based data.",
 "id": "GoogleCloudAiplatformV1beta1FileData",
@@ -837,7 +861,12 @@
 "GoogleCloudAiplatformV1beta1GoogleSearchRetrieval": {
 "description": "Tool to retrieve public web data for grounding, powered by Google.",
 "id": "GoogleCloudAiplatformV1beta1GoogleSearchRetrieval",
-"properties": {},
+"properties": {
+"dynamicRetrievalConfig": {
+"$ref": "GoogleCloudAiplatformV1beta1DynamicRetrievalConfig",
+"description": "Specifies the dynamic retrieval configuration for the given source."
+}
+},
 "type": "object"
 },
 "GoogleCloudAiplatformV1beta1GroundingChunk": {
@@ -903,6 +932,11 @@
 },
 "type": "array"
 },
+"retrievalMetadata": {
+"$ref": "GoogleCloudAiplatformV1beta1RetrievalMetadata",
+"description": "Optional. Output only. Retrieval metadata.",
+"readOnly": true
+},
 "retrievalQueries": {
 "description": "Optional. Queries executed by the retrieval tools.",
 "items": {
@@ -982,11 +1016,11 @@
 "type": "number"
 },
 "token": {
-"description": "The candidate\u2019s token string value.",
+"description": "The candidate's token string value.",
 "type": "string"
 },
 "tokenId": {
-"description": "The candidate\u2019s token id value.",
+"description": "The candidate's token id value.",
 "format": "int32",
 "type": "integer"
 }
@@ -1058,6 +1092,18 @@
 },
 "type": "object"
 },
+"GoogleCloudAiplatformV1beta1RetrievalMetadata": {
+"description": "Metadata related to retrieval in the grounding flow.",
+"id": "GoogleCloudAiplatformV1beta1RetrievalMetadata",
+"properties": {
+"googleSearchDynamicRetrievalScore": {
+"description": "Optional. Score indicating how likely information from google search could help answer the prompt. The score is in the range [0, 1], where 0 is the least likely and 1 is the most likely. This score is only populated when google search grounding and dynamic retrieval is enabled. It will be compared to the threshold to determine whether to trigger google search.",
+"format": "float",
+"type": "number"
+}
+},
+"type": "object"
+},
 "GoogleCloudAiplatformV1beta1SafetyRating": {
 "description": "Safety rating corresponding to the generated content.",
 "id": "GoogleCloudAiplatformV1beta1SafetyRating",
@@ -1206,6 +1252,13 @@
 "description": "Schema is used to define the format of input/output data. Represents a select subset of an [OpenAPI 3.0 schema object](https://spec.openapis.org/oas/v3.0.3#schema-object). More fields may be added in the future as needed.",
 "id": "GoogleCloudAiplatformV1beta1Schema",
 "properties": {
+"anyOf": {
+"description": "Optional. The value should be validated against any (one or more) of the subschemas in the list.",
+"items": {
+"$ref": "GoogleCloudAiplatformV1beta1Schema"
+},
+"type": "array"
+},
 "default": {
 "description": "Optional. Default value of the data.",
 "type": "any"

googleapiclient/discovery_cache/documents/gkehub.v1.json

@@ -2111,7 +2111,7 @@
 }
 }
 },
-"revision": "20240902",
+"revision": "20240920",
 "rootUrl": "https://gkehub.googleapis.com/",
 "schemas": {
 "AppDevExperienceFeatureSpec": {
@@ -6105,6 +6105,8 @@
 "CLUSTER_HAS_ZERO_NODES",
 "UNSUPPORTED_MULTIPLE_CONTROL_PLANES",
 "VPCSC_GA_SUPPORTED",
+"DEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT",
+"DEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT_SAFE",
 "CONFIG_APPLY_INTERNAL_ERROR",
 "CONFIG_VALIDATION_ERROR",
 "CONFIG_VALIDATION_WARNING",
@@ -6122,7 +6124,11 @@
 "QUOTA_EXCEEDED_SERVICE_LB_POLICIES",
 "QUOTA_EXCEEDED_HTTP_FILTERS",
 "QUOTA_EXCEEDED_TCP_FILTERS",
-"QUOTA_EXCEEDED_NETWORK_ENDPOINT_GROUPS"
+"QUOTA_EXCEEDED_NETWORK_ENDPOINT_GROUPS",
+"MODERNIZATION_SCHEDULED",
+"MODERNIZATION_IN_PROGRESS",
+"MODERNIZATION_COMPLETED",
+"MODERNIZATION_ABORTED"
 ],
 "enumDescriptions": [
 "Default Unspecified code",
@@ -6136,6 +6142,8 @@
 "Cluster has zero node code",
 "Multiple control planes unsupported error code",
 "VPC-SC GA is supported for this control plane.",
+"User is using deprecated ControlPlaneManagement and they have not yet set Management.",
+"User is using deprecated ControlPlaneManagement and they have already set Management.",
 "Configuration (Istio/k8s resources) failed to apply due to internal error.",
 "Configuration failed to be applied due to being invalid.",
 "Encountered configuration(s) with possible unintended behavior or invalid configuration. These configs may not have been applied.",
@@ -6153,7 +6161,11 @@
 "ServiceLBPolicy quota exceeded error code.",
 "HTTPFilter quota exceeded error code.",
 "TCPFilter quota exceeded error code.",
-"NetworkEndpointGroup quota exceeded error code."
+"NetworkEndpointGroup quota exceeded error code.",
+"Modernization is scheduled for a cluster.",
+"Modernization is in progress for a cluster.",
+"Modernization is completed for a cluster.",
+"Modernization is aborted for a cluster."
 ],
 "type": "string"
 },

googleapiclient/discovery_cache/documents/gkehub.v1alpha.json

@@ -2255,7 +2255,7 @@
 }
 }
 },
-"revision": "20240909",
+"revision": "20240920",
 "rootUrl": "https://gkehub.googleapis.com/",
 "schemas": {
 "AnthosObservabilityFeatureSpec": {
@@ -6714,6 +6714,8 @@
 "CLUSTER_HAS_ZERO_NODES",
 "UNSUPPORTED_MULTIPLE_CONTROL_PLANES",
 "VPCSC_GA_SUPPORTED",
+"DEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT",
+"DEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT_SAFE",
 "CONFIG_APPLY_INTERNAL_ERROR",
 "CONFIG_VALIDATION_ERROR",
 "CONFIG_VALIDATION_WARNING",
@@ -6731,7 +6733,11 @@
 "QUOTA_EXCEEDED_SERVICE_LB_POLICIES",
 "QUOTA_EXCEEDED_HTTP_FILTERS",
 "QUOTA_EXCEEDED_TCP_FILTERS",
-"QUOTA_EXCEEDED_NETWORK_ENDPOINT_GROUPS"
+"QUOTA_EXCEEDED_NETWORK_ENDPOINT_GROUPS",
+"MODERNIZATION_SCHEDULED",
+"MODERNIZATION_IN_PROGRESS",
+"MODERNIZATION_COMPLETED",
+"MODERNIZATION_ABORTED"
 ],
 "enumDescriptions": [
 "Default Unspecified code",
@@ -6745,6 +6751,8 @@
 "Cluster has zero node code",
 "Multiple control planes unsupported error code",
 "VPC-SC GA is supported for this control plane.",
+"User is using deprecated ControlPlaneManagement and they have not yet set Management.",
+"User is using deprecated ControlPlaneManagement and they have already set Management.",
 "Configuration (Istio/k8s resources) failed to apply due to internal error.",
 "Configuration failed to be applied due to being invalid.",
 "Encountered configuration(s) with possible unintended behavior or invalid configuration. These configs may not have been applied.",
@@ -6762,7 +6770,11 @@
 "ServiceLBPolicy quota exceeded error code.",
 "HTTPFilter quota exceeded error code.",
 "TCPFilter quota exceeded error code.",
-"NetworkEndpointGroup quota exceeded error code."
+"NetworkEndpointGroup quota exceeded error code.",
+"Modernization is scheduled for a cluster.",
+"Modernization is in progress for a cluster.",
+"Modernization is completed for a cluster.",
+"Modernization is aborted for a cluster."
 ],
 "type": "string"
 },

googleapiclient/discovery_cache/documents/gkehub.v1beta.json

@@ -2111,7 +2111,7 @@
 }
 }
 },
-"revision": "20240902",
+"revision": "20240920",
 "rootUrl": "https://gkehub.googleapis.com/",
 "schemas": {
 "AnthosObservabilityFeatureSpec": {
@@ -6268,6 +6268,8 @@
 "CLUSTER_HAS_ZERO_NODES",
 "UNSUPPORTED_MULTIPLE_CONTROL_PLANES",
 "VPCSC_GA_SUPPORTED",
+"DEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT",
+"DEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT_SAFE",
 "CONFIG_APPLY_INTERNAL_ERROR",
 "CONFIG_VALIDATION_ERROR",
 "CONFIG_VALIDATION_WARNING",
@@ -6285,7 +6287,11 @@
 "QUOTA_EXCEEDED_SERVICE_LB_POLICIES",
 "QUOTA_EXCEEDED_HTTP_FILTERS",
 "QUOTA_EXCEEDED_TCP_FILTERS",
-"QUOTA_EXCEEDED_NETWORK_ENDPOINT_GROUPS"
+"QUOTA_EXCEEDED_NETWORK_ENDPOINT_GROUPS",
+"MODERNIZATION_SCHEDULED",
+"MODERNIZATION_IN_PROGRESS",
+"MODERNIZATION_COMPLETED",
+"MODERNIZATION_ABORTED"
 ],
 "enumDescriptions": [
 "Default Unspecified code",
@@ -6299,6 +6305,8 @@
 "Cluster has zero node code",
 "Multiple control planes unsupported error code",
 "VPC-SC GA is supported for this control plane.",
+"User is using deprecated ControlPlaneManagement and they have not yet set Management.",
+"User is using deprecated ControlPlaneManagement and they have already set Management.",
 "Configuration (Istio/k8s resources) failed to apply due to internal error.",
 "Configuration failed to be applied due to being invalid.",
 "Encountered configuration(s) with possible unintended behavior or invalid configuration. These configs may not have been applied.",
@@ -6316,7 +6324,11 @@
 "ServiceLBPolicy quota exceeded error code.",
 "HTTPFilter quota exceeded error code.",
 "TCPFilter quota exceeded error code.",
-"NetworkEndpointGroup quota exceeded error code."
+"NetworkEndpointGroup quota exceeded error code.",
+"Modernization is scheduled for a cluster.",
+"Modernization is in progress for a cluster.",
+"Modernization is completed for a cluster.",
+"Modernization is aborted for a cluster."
 ],
 "type": "string"
 },

googleapiclient/discovery_cache/documents/healthcare.v1.json

@@ -4783,7 +4783,7 @@
 }
 }
 },
-"revision": "20240822",
+"revision": "20240910",
 "rootUrl": "https://healthcare.googleapis.com/",
 "schemas": {
 "ActivateConsentRequest": {
@@ -5586,7 +5586,7 @@
 },
 "notificationConfig": {
 "$ref": "NotificationConfig",
-"description": "Notification destination for new DICOM instances. Supplied by the client."
+"description": "Optional. 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.",
@@ -5963,15 +5963,15 @@
 "id": "FhirNotificationConfig",
 "properties": {
 "pubsubTopic": {
-"description": "The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. The notification is a `PubsubMessage` with 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. Note that 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. The Cloud Healthcare API service account, service-@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 (https://cloud.google.com/healthcare-api/docs/permissions-healthcare-api-gcp-products#dicom_fhir_and_hl7v2_store_cloud_pubsub_permissions). If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare-api/docs/how-tos/logging).",
+"description": "Optional. The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. The notification is a `PubsubMessage` with 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. Note that 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. The Cloud Healthcare API service account, service-@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 (https://cloud.google.com/healthcare-api/docs/permissions-healthcare-api-gcp-products#dicom_fhir_and_hl7v2_store_cloud_pubsub_permissions). If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare-api/docs/how-tos/logging).",
 "type": "string"
 },
 "sendFullResource": {
-"description": "Whether to send full FHIR resource to this Pub/Sub topic. The default value is false.",
+"description": "Optional. Whether to send full FHIR resource to this Pub/Sub topic. The default value is false.",
 "type": "boolean"
 },
 "sendPreviousResourceOnDelete": {
-"description": "Whether to send full FHIR resource to this Pub/Sub topic for deleting FHIR resource. The default value is false. Note that setting this to true does not guarantee that all previous resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the \"payloadType\" label from a Pub/Sub message to determine whether it needs to fetch the full previous resource as a separate operation.",
+"description": "Optional. Whether to send full FHIR resource to this Pub/Sub topic for deleting FHIR resource. The default value is false. Note that setting this to true does not guarantee that all previous resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the \"payloadType\" label from a Pub/Sub message to determine whether it needs to fetch the full previous resource as a separate operation.",
 "type": "boolean"
 }
 },
@@ -5996,7 +5996,7 @@
 "type": "string"
 },
 "defaultSearchHandlingStrict": {
-"description": "If true, overrides the default search behavior for this FHIR store to `handling=strict` which returns an error for unrecognized search parameters. If false, uses the FHIR specification default `handling=lenient` which ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP header `Prefer: handling=strict` or `Prefer: handling=lenient`. Defaults to false.",
+"description": "Optional. If true, overrides the default search behavior for this FHIR store to `handling=strict` which returns an error for unrecognized search parameters. If false, uses the FHIR specification default `handling=lenient` which ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP header `Prefer: handling=strict` or `Prefer: handling=lenient`. Defaults to false.",
 "type": "boolean"
 },
 "disableReferentialIntegrity": {
@@ -6008,7 +6008,7 @@
 "type": "boolean"
 },
 "enableUpdateCreate": {
-"description": "Whether this FHIR store has the [updateCreate capability](https://www.hl7.org/fhir/capabilitystatement-definitions.html#CapabilityStatement.rest.resource.updateCreate). This determines if the client can use an Update operation to create a new resource with a client-specified ID. If false, all IDs are server-assigned through the Create operation and attempts to update a non-existent resource return errors. It is strongly advised not to include or encode any sensitive data such as patient identifiers in client-specified resource IDs. Those IDs are part of the FHIR resource path recorded in Cloud audit logs and Pub/Sub notifications. Those IDs can also be contained in reference fields within other resources. Defaults to false.",
+"description": "Optional. Whether this FHIR store has the [updateCreate capability](https://www.hl7.org/fhir/capabilitystatement-definitions.html#CapabilityStatement.rest.resource.updateCreate). This determines if the client can use an Update operation to create a new resource with a client-specified ID. If false, all IDs are server-assigned through the Create operation and attempts to update a non-existent resource return errors. It is strongly advised not to include or encode any sensitive data such as patient identifiers in client-specified resource IDs. Those IDs are part of the FHIR resource path recorded in Cloud audit logs and Pub/Sub notifications. Those IDs can also be contained in reference fields within other resources. Defaults to false.",
 "type": "boolean"
 },
 "labels": {
@@ -6028,14 +6028,14 @@
 "description": "Deprecated. Use `notification_configs` instead. If non-empty, publish all resource modifications of this FHIR store to this destination. The Pub/Sub message attributes contain a map with a string describing the action that has triggered the notification. For example, \"action\":\"CreateResource\"."
 },
 "notificationConfigs": {
-"description": "Specifies where and whether to send notifications upon changes to a FHIR store.",
+"description": "Optional. Specifies where and whether to send notifications upon changes to a FHIR store.",
 "items": {
 "$ref": "FhirNotificationConfig"
 },
 "type": "array"
 },
 "streamConfigs": {
-"description": "A list of streaming configs that configure the destinations of streaming export for every resource mutation in this FHIR store. Each store is allowed to have up to 10 streaming configs. After a new config is added, the next resource mutation is streamed to the new location in addition to the existing ones. When a location is removed from the list, the server stops streaming to that location. Before adding a new config, you must add the required [`bigquery.dataEditor`](https://cloud.google.com/bigquery/docs/access-control#bigquery.dataEditor) role to your project's **Cloud Healthcare Service Agent** [service account](https://cloud.google.com/iam/docs/service-accounts). Some lag (typically on the order of dozens of seconds) is expected before the results show up in the streaming destination.",
+"description": "Optional. A list of streaming configs that configure the destinations of streaming export for every resource mutation in this FHIR store. Each store is allowed to have up to 10 streaming configs. After a new config is added, the next resource mutation is streamed to the new location in addition to the existing ones. When a location is removed from the list, the server stops streaming to that location. Before adding a new config, you must add the required [`bigquery.dataEditor`](https://cloud.google.com/bigquery/docs/access-control#bigquery.dataEditor) role to your project's **Cloud Healthcare Service Agent** [service account](https://cloud.google.com/iam/docs/service-accounts). Some lag (typically on the order of dozens of seconds) is expected before the results show up in the streaming destination.",
 "items": {
 "$ref": "StreamConfig"
 },
@@ -6330,19 +6330,19 @@
 "id": "GoogleCloudHealthcareV1FhirBigQueryDestination",
 "properties": {
 "datasetUri": {
-"description": "BigQuery URI to an existing dataset, up to 2000 characters long, in the format `bq://projectId.bqDatasetId`.",
+"description": "Optional. BigQuery URI to an existing dataset, up to 2000 characters long, in the format `bq://projectId.bqDatasetId`.",
 "type": "string"
 },
 "force": {
-"description": "The default value is false. If this flag is `TRUE`, all tables are deleted from the dataset before the new exported tables are written. If the flag is not set and the destination dataset contains tables, the export call returns an error. If `write_disposition` is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.",
+"description": "Optional. The default value is false. If this flag is `TRUE`, all tables are deleted from the dataset before the new exported tables are written. If the flag is not set and the destination dataset contains tables, the export call returns an error. If `write_disposition` is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.",
 "type": "boolean"
 },
 "schemaConfig": {
 "$ref": "SchemaConfig",
-"description": "The configuration for the exported BigQuery schema."
+"description": "Optional. The configuration for the exported BigQuery schema."
 },
 "writeDisposition": {
-"description": "Determines if existing data in the destination dataset is overwritten, appended to, or not written if the tables contain data. If a write_disposition is specified, the `force` parameter is ignored.",
+"description": "Optional. Determines if existing data in the destination dataset is overwritten, appended to, or not written if the tables contain data. If a write_disposition is specified, the `force` parameter is ignored.",
 "enum": [
 "WRITE_DISPOSITION_UNSPECIFIED",
 "WRITE_EMPTY",
@@ -6442,7 +6442,7 @@
 "id": "Hl7V2NotificationConfig",
 "properties": {
 "filter": {
-"description": "Restricts notifications sent for messages matching a filter. If this is empty, all messages are matched. 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 `yyyy-mm-dd` form. 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, it's 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\"`. * `PatientId(value, type)`, which matches if the message lists a patient having an ID of the given value and type in the PID-2, PID-3, or PID-4 segments. For example, `PatientId(\"123456\", \"MRN\")`. * `labels.x`, a string value of the label with key `x` as set using the Message.labels map. For example, `labels.\"priority\"=\"high\"`. The operator `:*` can be used to assert the existence of a label. For example, `labels.\"priority\":*`.",
+"description": "Optional. Restricts notifications sent for messages matching a filter. If this is empty, all messages are matched. 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 `yyyy-mm-dd` form. 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, it's 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\"`. * `PatientId(value, type)`, which matches if the message lists a patient having an ID of the given value and type in the PID-2, PID-3, or PID-4 segments. For example, `PatientId(\"123456\", \"MRN\")`. * `labels.x`, a string value of the label with key `x` as set using the Message.labels map. For example, `labels.\"priority\"=\"high\"`. The operator `:*` can be used to assert the existence of a label. For example, `labels.\"priority\":*`.",
 "type": "string"
 },
 "pubsubTopic": {
@@ -6468,7 +6468,7 @@
 "type": "string"
 },
 "notificationConfigs": {
-"description": "A list of notification configs. Each configuration uses a filter to determine whether to publish a message (both Ingest & Create) on the corresponding notification destination. Only the message name is sent as part of the notification. Supplied by the client.",
+"description": "Optional. A list of notification configs. Each configuration uses a filter to determine whether to publish a message (both Ingest & Create) on the corresponding notification destination. Only the message name is sent as part of the notification. Supplied by the client.",
 "items": {
 "$ref": "Hl7V2NotificationConfig"
 },
@@ -6476,10 +6476,10 @@
 },
 "parserConfig": {
 "$ref": "ParserConfig",
-"description": "The configuration for the parser. It determines how the server parses the messages."
+"description": "Optional. The configuration for the parser. It determines how the server parses the messages."
 },
 "rejectDuplicateMessage": {
-"description": "Determines whether to reject duplicate messages. A duplicate message is a message with the same raw bytes as a message that has already been ingested/created in this HL7v2 store. The default value is false, meaning that the store accepts the duplicate messages and it also returns the same ACK message in the IngestMessageResponse as has been returned previously. Note that only one resource is created in the store. When this field is set to true, CreateMessage/IngestMessage requests with a duplicate message will be rejected by the store, and IngestMessageErrorDetail returns a NACK message upon rejection.",
+"description": "Optional. Determines whether to reject duplicate messages. A duplicate message is a message with the same raw bytes as a message that has already been ingested/created in this HL7v2 store. The default value is false, meaning that the store accepts the duplicate messages and it also returns the same ACK message in the IngestMessageResponse as has been returned previously. Note that only one resource is created in the store. When this field is set to true, CreateMessage/IngestMessage requests with a duplicate message will be rejected by the store, and IngestMessageErrorDetail returns a NACK message upon rejection.",
 "type": "boolean"
 }
 },
@@ -7177,12 +7177,12 @@
 "id": "ParserConfig",
 "properties": {
 "allowNullHeader": {
-"description": "Determines whether messages with no header are allowed.",
+"description": "Optional. Determines whether messages with no header are allowed.",
 "type": "boolean"
 },
 "schema": {
 "$ref": "SchemaPackage",
-"description": "Schemas used to parse messages in this store, if schematized parsing is desired."
+"description": "Optional. Schemas used to parse messages in this store, if schematized parsing is desired."
 },
 "segmentTerminator": {
 "description": "Byte(s) to use as the segment terminator. If this is unset, '\\r' is used as segment terminator, matching the HL7 version 2 specification.",
@@ -7624,18 +7624,18 @@
 "id": "SchemaPackage",
 "properties": {
 "ignoreMinOccurs": {
-"description": "Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.",
+"description": "Optional. Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.",
 "type": "boolean"
 },
 "schemas": {
-"description": "Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.",
+"description": "Optional. Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.",
 "items": {
 "$ref": "Hl7SchemaConfig"
 },
 "type": "array"
 },
 "schematizedParsingType": {
-"description": "Determines how messages that fail to parse are handled.",
+"description": "Optional. Determines how messages that fail to parse are handled.",
 "enum": [
 "SCHEMATIZED_PARSING_TYPE_UNSPECIFIED",
 "SOFT_FAIL",
@@ -7649,14 +7649,14 @@
 "type": "string"
 },
 "types": {
-"description": "Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.",
+"description": "Optional. Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.",
 "items": {
 "$ref": "Hl7TypesConfig"
 },
 "type": "array"
 },
 "unexpectedSegmentHandling": {
-"description": "Determines how unexpected segments (segments not matched to the schema) are handled.",
+"description": "Optional. Determines how unexpected segments (segments not matched to the schema) are handled.",
 "enum": [
 "UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED",
 "FAIL",
@@ -7885,14 +7885,14 @@
 "properties": {
 "bigqueryDestination": {
 "$ref": "GoogleCloudHealthcareV1FhirBigQueryDestination",
-"description": "The destination BigQuery structure that contains both the dataset location and corresponding schema config. The output is organized in one table per resource type. The server reuses the existing tables (if any) that are named after the resource types. For example, \"Patient\", \"Observation\". When there is no existing table for a given resource type, the server attempts to create one. When a table schema doesn't align with the schema config, either because of existing incompatible schema or out of band incompatible modification, the server does not stream in new data. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data is not streamed. 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. Results are written to BigQuery tables according to the parameters in BigQueryDestination.WriteDisposition. Different versions of the same resource are distinguishable by the meta.versionId and meta.lastUpdated columns. The operation (CREATE/UPDATE/DELETE) that results in the new version is recorded in the meta.tag. The tables contain all historical resource versions since streaming was enabled. For query convenience, the server also creates one view per table of the same name containing only the current resource version. The streamed data in the BigQuery dataset is not guaranteed to be completely unique. The combination of the id and meta.versionId columns should ideally identify a single unique row. But in rare cases, duplicates may exist. At query time, users may use the SQL select statement to keep only one of the duplicate rows given an id and meta.versionId pair. Alternatively, the server created view mentioned above also filters out duplicates. If a resource mutation cannot be streamed to BigQuery, errors are logged to Cloud Logging. For more information, see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging))."
+"description": "Optional. The destination BigQuery structure that contains both the dataset location and corresponding schema config. The output is organized in one table per resource type. The server reuses the existing tables (if any) that are named after the resource types. For example, \"Patient\", \"Observation\". When there is no existing table for a given resource type, the server attempts to create one. When a table schema doesn't align with the schema config, either because of existing incompatible schema or out of band incompatible modification, the server does not stream in new data. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data is not streamed. 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. Results are written to BigQuery tables according to the parameters in BigQueryDestination.WriteDisposition. Different versions of the same resource are distinguishable by the meta.versionId and meta.lastUpdated columns. The operation (CREATE/UPDATE/DELETE) that results in the new version is recorded in the meta.tag. The tables contain all historical resource versions since streaming was enabled. For query convenience, the server also creates one view per table of the same name containing only the current resource version. The streamed data in the BigQuery dataset is not guaranteed to be completely unique. The combination of the id and meta.versionId columns should ideally identify a single unique row. But in rare cases, duplicates may exist. At query time, users may use the SQL select statement to keep only one of the duplicate rows given an id and meta.versionId pair. Alternatively, the server created view mentioned above also filters out duplicates. If a resource mutation cannot be streamed to BigQuery, errors are logged to Cloud Logging. For more information, see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging))."
 },
 "deidentifiedStoreDestination": {
 "$ref": "DeidentifiedStoreDestination",
 "description": "The destination FHIR store for de-identified resources. After this field is added, all subsequent creates/updates/patches to the source store will be de-identified using the provided configuration and applied to the destination store. Importing resources to the source store will not trigger the streaming. If the source store already contains resources when this option is enabled, those resources will not be copied to the destination store unless they are subsequently updated. This may result in invalid references in the destination store. Before adding this config, you must grant the healthcare.fhirResources.update permission on the destination store to your project's **Cloud Healthcare Service Agent** [service account](https://cloud.google.com/healthcare/docs/how-tos/permissions-healthcare-api-gcp-products#the_cloud_healthcare_service_agent). The destination store must set enable_update_create to true. The destination store must have disable_referential_integrity set to true. If a resource cannot be de-identified, errors will be logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging))."
 },
 "resourceTypes": {
-"description": "Supply a FHIR resource type (such as \"Patient\" or \"Observation\"). See https://www.hl7.org/fhir/valueset-resource-types.html for a list of all FHIR resource types. The server treats an empty list as an intent to stream all the supported resource types in this FHIR store.",
+"description": "Optional. Supply a FHIR resource type (such as \"Patient\" or \"Observation\"). See https://www.hl7.org/fhir/valueset-resource-types.html for a list of all FHIR resource types. The server treats an empty list as an intent to stream all the supported resource types in this FHIR store.",
 "items": {
 "type": "string"
 },

googleapiclient/discovery_cache/documents/iam.v1.json

@@ -3188,7 +3188,7 @@
 }
 }
 },
-"revision": "20240725",
+"revision": "20240918",
 "rootUrl": "https://iam.googleapis.com/",
 "schemas": {
 "AccessRestrictions": {
@@ -3555,7 +3555,7 @@
 ],
 "enumDescriptions": [
 "No AttributesType specified.",
-"Used to get the user's group claims from the Azure AD identity provider using configuration provided in ExtraAttributesOAuth2Client and `mail` property of the `microsoft.graph.group` object is used for claim mapping. See https://learn.microsoft.com/en-us/graph/api/resources/group?view=graph-rest-1.0#properties for more details on `microsoft.graph.group` properties. The attributes obtained from idntity provider are mapped to `assertion.groups`."
+"Used to get the user's group claims from the Microsoft Entra ID identity provider using configuration provided in ExtraAttributesOAuth2Client and `mail` property of the `microsoft.graph.group` object is used for claim mapping. See https://learn.microsoft.com/en-us/graph/api/resources/group?view=graph-rest-1.0#properties for more details on `microsoft.graph.group` properties. The attributes obtained from idntity provider are mapped to `assertion.groups`."
 ],
 "type": "string"
 },