google-api-python-client 2.176.0__py3-none-any.whl → 2.178.0__py3-none-any.whl

googleapiclient/discovery_cache/documents/gkehub.v2.json

@@ -477,7 +477,7 @@
 }
 }
 },
-"revision": "20250612",
+"revision": "20250720",
 "rootUrl": "https://gkehub.googleapis.com/",
 "schemas": {
 "AppDevExperienceState": {
@@ -626,7 +626,8 @@
 "IN_PROGRESS",
 "SOAKING",
 "FORCED_SOAKING",
-"COMPLETE"
+"COMPLETE",
+"FORCED_COMPLETE"
 ],
 "enumDescriptions": [
 "Required by https://linter.aip.dev/126/unspecified.",
@@ -635,7 +636,8 @@
 "The upgrade is in progress. At the scope level, this means the upgrade is in progress for at least one cluster in the scope.",
 "The upgrade has finished and is soaking until the soaking time is up. At the scope level, this means at least one cluster is in soaking while the rest are either soaking or complete.",
 "A cluster will be forced to enter soaking if an upgrade doesn't finish within a certain limit, despite it's actual status.",
-"The upgrade has passed all post conditions (soaking). At the scope level, this means all eligible clusters are in COMPLETE status."
+"The upgrade has passed all post conditions (soaking). At the scope level, this means all eligible clusters are in COMPLETE status.",
+"The upgrade was forced into soaking and the soaking time has passed. This is the equivalent of COMPLETE status for upgrades that were forced into soaking."
 ],
 "type": "string"
 },
@@ -3176,7 +3178,8 @@
 "ACTIVE",
 "STALLED",
 "NEEDS_ATTENTION",
-"DEGRADED"
+"DEGRADED",
+"DEPROVISIONING"
 ],
 "enumDescriptions": [
 "Unspecified",
@@ -3186,7 +3189,8 @@
 "ACTIVE means that the component is ready for use.",
 "STALLED means that provisioning could not be done.",
 "NEEDS_ATTENTION means that the component is ready, but some user intervention is required. (For example that the user should migrate workloads to a new control plane revision.)",
-"DEGRADED means that the component is ready, but operating in a degraded state."
+"DEGRADED means that the component is ready, but operating in a degraded state.",
+"DEPROVISIONING means that deprovisioning is in progress."
 ],
 "type": "string"
 }
@@ -3214,7 +3218,8 @@
 "ACTIVE",
 "STALLED",
 "NEEDS_ATTENTION",
-"DEGRADED"
+"DEGRADED",
+"DEPROVISIONING"
 ],
 "enumDescriptions": [
 "Unspecified",
@@ -3224,7 +3229,8 @@
 "ACTIVE means that the component is ready for use.",
 "STALLED means that provisioning could not be done.",
 "NEEDS_ATTENTION means that the component is ready, but some user intervention is required. (For example that the user should migrate workloads to a new control plane revision.)",
-"DEGRADED means that the component is ready, but operating in a degraded state."
+"DEGRADED means that the component is ready, but operating in a degraded state.",
+"DEPROVISIONING means that deprovisioning is in progress."
 ],
 "type": "string"
 }
@@ -3286,12 +3292,14 @@
 "enum": [
 "MANAGEMENT_UNSPECIFIED",
 "MANAGEMENT_AUTOMATIC",
-"MANAGEMENT_MANUAL"
+"MANAGEMENT_MANUAL",
+"MANAGEMENT_NOT_INSTALLED"
 ],
 "enumDescriptions": [
 "Unspecified",
 "Google should manage my Service Mesh for the cluster.",
-"User will manually configure their service mesh components."
+"User will manually configure their service mesh components.",
+"Google should remove any managed Service Mesh components from this cluster and deprovision any resources."
 ],
 "type": "string"
 }

googleapiclient/discovery_cache/documents/gkehub.v2alpha.json

@@ -477,7 +477,7 @@
 }
 }
 },
-"revision": "20250612",
+"revision": "20250720",
 "rootUrl": "https://gkehub.googleapis.com/",
 "schemas": {
 "AppDevExperienceState": {
@@ -626,7 +626,8 @@
 "IN_PROGRESS",
 "SOAKING",
 "FORCED_SOAKING",
-"COMPLETE"
+"COMPLETE",
+"FORCED_COMPLETE"
 ],
 "enumDescriptions": [
 "Required by https://linter.aip.dev/126/unspecified.",
@@ -635,7 +636,8 @@
 "The upgrade is in progress. At the scope level, this means the upgrade is in progress for at least one cluster in the scope.",
 "The upgrade has finished and is soaking until the soaking time is up. At the scope level, this means at least one cluster is in soaking while the rest are either soaking or complete.",
 "A cluster will be forced to enter soaking if an upgrade doesn't finish within a certain limit, despite it's actual status.",
-"The upgrade has passed all post conditions (soaking). At the scope level, this means all eligible clusters are in COMPLETE status."
+"The upgrade has passed all post conditions (soaking). At the scope level, this means all eligible clusters are in COMPLETE status.",
+"The upgrade was forced into soaking and the soaking time has passed. This is the equivalent of COMPLETE status for upgrades that were forced into soaking."
 ],
 "type": "string"
 },
@@ -3176,7 +3178,8 @@
 "ACTIVE",
 "STALLED",
 "NEEDS_ATTENTION",
-"DEGRADED"
+"DEGRADED",
+"DEPROVISIONING"
 ],
 "enumDescriptions": [
 "Unspecified",
@@ -3186,7 +3189,8 @@
 "ACTIVE means that the component is ready for use.",
 "STALLED means that provisioning could not be done.",
 "NEEDS_ATTENTION means that the component is ready, but some user intervention is required. (For example that the user should migrate workloads to a new control plane revision.)",
-"DEGRADED means that the component is ready, but operating in a degraded state."
+"DEGRADED means that the component is ready, but operating in a degraded state.",
+"DEPROVISIONING means that deprovisioning is in progress."
 ],
 "type": "string"
 }
@@ -3214,7 +3218,8 @@
 "ACTIVE",
 "STALLED",
 "NEEDS_ATTENTION",
-"DEGRADED"
+"DEGRADED",
+"DEPROVISIONING"
 ],
 "enumDescriptions": [
 "Unspecified",
@@ -3224,7 +3229,8 @@
 "ACTIVE means that the component is ready for use.",
 "STALLED means that provisioning could not be done.",
 "NEEDS_ATTENTION means that the component is ready, but some user intervention is required. (For example that the user should migrate workloads to a new control plane revision.)",
-"DEGRADED means that the component is ready, but operating in a degraded state."
+"DEGRADED means that the component is ready, but operating in a degraded state.",
+"DEPROVISIONING means that deprovisioning is in progress."
 ],
 "type": "string"
 }
@@ -3286,12 +3292,14 @@
 "enum": [
 "MANAGEMENT_UNSPECIFIED",
 "MANAGEMENT_AUTOMATIC",
-"MANAGEMENT_MANUAL"
+"MANAGEMENT_MANUAL",
+"MANAGEMENT_NOT_INSTALLED"
 ],
 "enumDescriptions": [
 "Unspecified",
 "Google should manage my Service Mesh for the cluster.",
-"User will manually configure their service mesh components."
+"User will manually configure their service mesh components.",
+"Google should remove any managed Service Mesh components from this cluster and deprovision any resources."
 ],
 "type": "string"
 }

googleapiclient/discovery_cache/documents/gkehub.v2beta.json

@@ -477,7 +477,7 @@
 }
 }
 },
-"revision": "20250612",
+"revision": "20250720",
 "rootUrl": "https://gkehub.googleapis.com/",
 "schemas": {
 "AppDevExperienceState": {
@@ -626,7 +626,8 @@
 "IN_PROGRESS",
 "SOAKING",
 "FORCED_SOAKING",
-"COMPLETE"
+"COMPLETE",
+"FORCED_COMPLETE"
 ],
 "enumDescriptions": [
 "Required by https://linter.aip.dev/126/unspecified.",
@@ -635,7 +636,8 @@
 "The upgrade is in progress. At the scope level, this means the upgrade is in progress for at least one cluster in the scope.",
 "The upgrade has finished and is soaking until the soaking time is up. At the scope level, this means at least one cluster is in soaking while the rest are either soaking or complete.",
 "A cluster will be forced to enter soaking if an upgrade doesn't finish within a certain limit, despite it's actual status.",
-"The upgrade has passed all post conditions (soaking). At the scope level, this means all eligible clusters are in COMPLETE status."
+"The upgrade has passed all post conditions (soaking). At the scope level, this means all eligible clusters are in COMPLETE status.",
+"The upgrade was forced into soaking and the soaking time has passed. This is the equivalent of COMPLETE status for upgrades that were forced into soaking."
 ],
 "type": "string"
 },
@@ -3176,7 +3178,8 @@
 "ACTIVE",
 "STALLED",
 "NEEDS_ATTENTION",
-"DEGRADED"
+"DEGRADED",
+"DEPROVISIONING"
 ],
 "enumDescriptions": [
 "Unspecified",
@@ -3186,7 +3189,8 @@
 "ACTIVE means that the component is ready for use.",
 "STALLED means that provisioning could not be done.",
 "NEEDS_ATTENTION means that the component is ready, but some user intervention is required. (For example that the user should migrate workloads to a new control plane revision.)",
-"DEGRADED means that the component is ready, but operating in a degraded state."
+"DEGRADED means that the component is ready, but operating in a degraded state.",
+"DEPROVISIONING means that deprovisioning is in progress."
 ],
 "type": "string"
 }
@@ -3214,7 +3218,8 @@
 "ACTIVE",
 "STALLED",
 "NEEDS_ATTENTION",
-"DEGRADED"
+"DEGRADED",
+"DEPROVISIONING"
 ],
 "enumDescriptions": [
 "Unspecified",
@@ -3224,7 +3229,8 @@
 "ACTIVE means that the component is ready for use.",
 "STALLED means that provisioning could not be done.",
 "NEEDS_ATTENTION means that the component is ready, but some user intervention is required. (For example that the user should migrate workloads to a new control plane revision.)",
-"DEGRADED means that the component is ready, but operating in a degraded state."
+"DEGRADED means that the component is ready, but operating in a degraded state.",
+"DEPROVISIONING means that deprovisioning is in progress."
 ],
 "type": "string"
 }
@@ -3286,12 +3292,14 @@
 "enum": [
 "MANAGEMENT_UNSPECIFIED",
 "MANAGEMENT_AUTOMATIC",
-"MANAGEMENT_MANUAL"
+"MANAGEMENT_MANUAL",
+"MANAGEMENT_NOT_INSTALLED"
 ],
 "enumDescriptions": [
 "Unspecified",
 "Google should manage my Service Mesh for the cluster.",
-"User will manually configure their service mesh components."
+"User will manually configure their service mesh components.",
+"Google should remove any managed Service Mesh components from this cluster and deprovision any resources."
 ],
 "type": "string"
 }

googleapiclient/discovery_cache/documents/healthcare.v1.json

@@ -2412,7 +2412,7 @@
 ]
 },
 "retrieveMetadata": {
-"description": "RetrieveStudyMetadata returns instance associated with the given study presented as metadata with the bulk data removed. See [RetrieveTransaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveStudyMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveStudyMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
+"description": "RetrieveStudyMetadata returns instance associated with the given study presented as metadata. See [RetrieveTransaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveStudyMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveStudyMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
 "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/dicomStores/{dicomStoresId}/dicomWeb/studies/{studiesId}/metadata",
 "httpMethod": "GET",
 "id": "healthcare.projects.locations.datasets.dicomStores.studies.retrieveMetadata",
@@ -2623,7 +2623,7 @@
 ]
 },
 "retrieveMetadata": {
-"description": "RetrieveSeriesMetadata returns instance associated with the given study and series, presented as metadata with the bulk data removed. See [RetrieveTransaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveSeriesMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveSeriesMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
+"description": "RetrieveSeriesMetadata returns instance associated with the given study and series, presented as metadata. See [RetrieveTransaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveSeriesMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveSeriesMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
 "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/dicomStores/{dicomStoresId}/dicomWeb/studies/{studiesId}/series/{seriesId}/metadata",
 "httpMethod": "GET",
 "id": "healthcare.projects.locations.datasets.dicomStores.studies.series.retrieveMetadata",
@@ -2797,7 +2797,7 @@
 ]
 },
 "retrieveMetadata": {
-"description": "RetrieveInstanceMetadata returns instance associated with the given study, series, and SOP Instance UID presented as metadata with the bulk data removed. See [RetrieveTransaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveInstanceMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveInstanceMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
+"description": "RetrieveInstanceMetadata returns instance associated with the given study, series, and SOP Instance UID presented as metadata. See [RetrieveTransaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveInstanceMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveInstanceMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
 "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/dicomStores/{dicomStoresId}/dicomWeb/studies/{studiesId}/series/{seriesId}/instances/{instancesId}/metadata",
 "httpMethod": "GET",
 "id": "healthcare.projects.locations.datasets.dicomStores.studies.series.instances.retrieveMetadata",
@@ -2871,6 +2871,44 @@
 }
 },
 "resources": {
+"bulkdata": {
+"methods": {
+"retrieveBulkdata": {
+"description": "Returns uncompressed, unencoded bytes representing the referenced bulkdata tag from an instance. See [Retrieve Transaction](http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveBulkdata, see [Bulkdata resources](https://cloud.google.com/healthcare/docs/dicom#bulkdata-resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveBulkdata, see [Retrieve bulkdata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-bulkdata).",
+"flatPath": "v1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/dicomStores/{dicomStoresId}/dicomWeb/studies/{studiesId}/series/{seriesId}/instances/{instancesId}/bulkdata/{bulkdataId}/{bulkdataId1}",
+"httpMethod": "GET",
+"id": "healthcare.projects.locations.datasets.dicomStores.studies.series.instances.bulkdata.retrieveBulkdata",
+"parameterOrder": [
+"parent",
+"dicomWebPath"
+],
+"parameters": {
+"dicomWebPath": {
+"description": "Required. The path for the `RetrieveBulkdata` DICOMweb request. For example, `studies/{study_uid}/series/{series_uid}/instances/{instance_uid}/bukdata/{bulkdata_uri}`.",
+"location": "path",
+"pattern": "^studies/[^/]+/series/[^/]+/instances/[^/]+/bulkdata/[^/]+/.*$",
+"required": true,
+"type": "string"
+},
+"parent": {
+"description": "Required. The name of the DICOM store that is being accessed. For example, `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`.",
+"location": "path",
+"pattern": "^projects/[^/]+/locations/[^/]+/datasets/[^/]+/dicomStores/[^/]+$",
+"required": true,
+"type": "string"
+}
+},
+"path": "v1/{+parent}/dicomWeb/{+dicomWebPath}",
+"response": {
+"$ref": "HttpBody"
+},
+"scopes": [
+"https://www.googleapis.com/auth/cloud-healthcare",
+"https://www.googleapis.com/auth/cloud-platform"
+]
+}
+}
+},
 "frames": {
 "methods": {
 "retrieveFrames": {
@@ -4225,7 +4263,7 @@
 ]
 },
 "update": {
-"description": "Updates the entire contents of a resource. Implements the FHIR standard update interaction ([DSTU2](https://hl7.org/fhir/DSTU2/http.html#update), [STU3](https://hl7.org/fhir/STU3/http.html#update), [R4](https://hl7.org/fhir/R4/http.html#update), [R5](https://hl7.org/fhir/R5/http.html#update)). If the specified resource does not exist and the FHIR store has enable_update_create set, creates the resource with the client-specified ID. 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. The request body must contain a JSON-encoded FHIR resource, and the request headers must contain `Content-Type: application/fhir+json`. The resource must contain an `id` element having an identical value to the ID in the REST path of the request. On success, the response body contains a JSON-encoded representation of the updated resource, including the server-assigned version ID. Errors generated by the FHIR store contain a JSON-encoded `OperationOutcome` resource describing the reason for the error. If the request cannot be mapped to a valid API method on a FHIR store, a generic GCP error might be returned instead. In R5, the conditional update interaction If-None-Match is supported, including the wildcard behaviour. For samples that show how to call `update`, see [Updating a FHIR resource](https://cloud.google.com/healthcare/docs/how-tos/fhir-resources#updating_a_fhir_resource).",
+"description": "Updates the entire contents of a resource. Implements the FHIR standard update interaction ([DSTU2](https://hl7.org/fhir/DSTU2/http.html#update), [STU3](https://hl7.org/fhir/STU3/http.html#update), [R4](https://hl7.org/fhir/R4/http.html#update), [R5](https://hl7.org/fhir/R5/http.html#update)). If the specified resource does not exist and the FHIR store has enable_update_create set, creates the resource with the client-specified ID. 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. The request body must contain a JSON-encoded FHIR resource, and the request headers must contain `Content-Type: application/fhir+json`. The resource must contain an `id` element having an identical value to the ID in the REST path of the request. On success, the response body contains a JSON-encoded representation of the updated resource, including the server-assigned version ID. Errors generated by the FHIR store contain a JSON-encoded `OperationOutcome` resource describing the reason for the error. If the request cannot be mapped to a valid API method on a FHIR store, a generic GCP error might be returned instead. The conditional update interaction If-None-Match is supported, including the wildcard behaviour, as defined by the R5 spec. This functionality is supported in R4 and R5. For samples that show how to call `update`, see [Updating a FHIR resource](https://cloud.google.com/healthcare/docs/how-tos/fhir-resources#updating_a_fhir_resource).",
 "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/fhirStores/{fhirStoresId}/fhir/{fhirId}/{fhirId1}",
 "httpMethod": "PUT",
 "id": "healthcare.projects.locations.datasets.fhirStores.fhir.update",
@@ -5094,7 +5132,7 @@
 }
 }
 },
-"revision": "20250526",
+"revision": "20250710",
 "rootUrl": "https://healthcare.googleapis.com/",
 "schemas": {
 "AccessDeterminationLogConfig": {
@@ -6134,6 +6172,17 @@
 },
 "type": "object"
 },
+"DicomNotificationConfig": {
+"description": "Contains the configuration for DICOM notifications.",
+"id": "DicomNotificationConfig",
+"properties": {
+"pubsubTopic": {
+"description": "Required. 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. * `PubsubMessage.Attributes` contains the following attributes: * `action`: The name of the endpoint that generated the notification. Possible values are `StoreInstances`, `SetBlobSettings`, `ImportDicomData`, etc. * `lastUpdatedTime`: The latest timestamp when the DICOM instance was updated. * `storeName`: The resource name of the DICOM store, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`. * `studyInstanceUID`: The study UID of the DICOM instance that was changed. * `seriesInstanceUID`: The series UID of the DICOM instance that was changed. * `sopInstanceUID`: The instance UID of the DICOM instance that was changed. * `versionId`: The version ID of the DICOM instance that was changed. * `modality`: The modality tag of the DICOM instance that was changed. * `previousStorageClass`: The storage class where the DICOM instance was previously stored if the storage class was changed. * `storageClass`: The storage class where the DICOM instance is currently stored. 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 the `pubsub.topics.publish` permission (which is typically included in `roles/pubsub.publisher` role) 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"
+}
+},
+"type": "object"
+},
 "DicomStore": {
 "description": "Represents a DICOM store.",
 "id": "DicomStore",
@@ -6153,6 +6202,13 @@
 "$ref": "NotificationConfig",
 "description": "Optional. Notification destination for new DICOM instances. Supplied by the client."
 },
+"notificationConfigs": {
+"description": "Optional. Specifies where and whether to send notifications upon changes to a DICOM store.",
+"items": {
+"$ref": "DicomNotificationConfig"
+},
+"type": "array"
+},
 "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": {

googleapiclient/discovery_cache/documents/healthcare.v1beta1.json

@@ -2506,7 +2506,7 @@
 ]
 },
 "retrieveMetadata": {
-"description": "RetrieveStudyMetadata returns instance associated with the given study presented as metadata with the bulk data removed. See [RetrieveTransaction](http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveStudyMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveStudyMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
+"description": "RetrieveStudyMetadata returns instance associated with the given study presented as metadata. See [RetrieveTransaction](http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveStudyMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveStudyMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
 "flatPath": "v1beta1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/dicomStores/{dicomStoresId}/dicomWeb/studies/{studiesId}/metadata",
 "httpMethod": "GET",
 "id": "healthcare.projects.locations.datasets.dicomStores.studies.retrieveMetadata",
@@ -2717,7 +2717,7 @@
 ]
 },
 "retrieveMetadata": {
-"description": "RetrieveSeriesMetadata returns instance associated with the given study and series, presented as metadata with the bulk data removed. See [RetrieveTransaction](http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveSeriesMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveSeriesMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
+"description": "RetrieveSeriesMetadata returns instance associated with the given study and series, presented as metadata. See [RetrieveTransaction](http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveSeriesMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveSeriesMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
 "flatPath": "v1beta1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/dicomStores/{dicomStoresId}/dicomWeb/studies/{studiesId}/series/{seriesId}/metadata",
 "httpMethod": "GET",
 "id": "healthcare.projects.locations.datasets.dicomStores.studies.series.retrieveMetadata",
@@ -2891,7 +2891,7 @@
 ]
 },
 "retrieveMetadata": {
-"description": "RetrieveInstanceMetadata returns instance associated with the given study, series, and SOP Instance UID presented as metadata with the bulk data removed. See [RetrieveTransaction](http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveInstanceMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveInstanceMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
+"description": "RetrieveInstanceMetadata returns instance associated with the given study, series, and SOP Instance UID presented as metadata. See [RetrieveTransaction](http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveInstanceMetadata, see [Metadata resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveInstanceMetadata, see [Retrieve metadata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).",
 "flatPath": "v1beta1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/dicomStores/{dicomStoresId}/dicomWeb/studies/{studiesId}/series/{seriesId}/instances/{instancesId}/metadata",
 "httpMethod": "GET",
 "id": "healthcare.projects.locations.datasets.dicomStores.studies.series.instances.retrieveMetadata",
@@ -2968,7 +2968,7 @@
 "bulkdata": {
 "methods": {
 "retrieveBulkdata": {
-"description": "Returns uncompressed, unencoded bytes representing the referenced bulkdata tag from an instance. See [Retrieve Transaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4){: .external}. For details on the implementation of RetrieveBulkdata, see [Bulkdata resources](https://cloud.google.com/healthcare/docs/dicom#bulkdata-resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveBulkdata, see [Retrieve bulkdata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-bulkdata).",
+"description": "Returns uncompressed, unencoded bytes representing the referenced bulkdata tag from an instance. See [Retrieve Transaction](http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.4). For details on the implementation of RetrieveBulkdata, see [Bulkdata resources](https://cloud.google.com/healthcare/docs/dicom#bulkdata-resources) in the Cloud Healthcare API conformance statement. For samples that show how to call RetrieveBulkdata, see [Retrieve bulkdata](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-bulkdata).",
 "flatPath": "v1beta1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/dicomStores/{dicomStoresId}/dicomWeb/studies/{studiesId}/series/{seriesId}/instances/{instancesId}/bulkdata/{bulkdataId}/{bulkdataId1}",
 "httpMethod": "GET",
 "id": "healthcare.projects.locations.datasets.dicomStores.studies.series.instances.bulkdata.retrieveBulkdata",
@@ -4666,7 +4666,7 @@
 ]
 },
 "update": {
-"description": "Updates the entire contents of a resource. Implements the FHIR standard update interaction ([DSTU2](https://hl7.org/fhir/DSTU2/http.html#update), [STU3](https://hl7.org/fhir/STU3/http.html#update), [R4](https://hl7.org/fhir/R4/http.html#update), [R5](https://hl7.org/fhir/R5/http.html#update)). If the specified resource does not exist and the FHIR store has enable_update_create set, creates the resource with the client-specified ID. 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. The request body must contain a JSON-encoded FHIR resource, and the request headers must contain `Content-Type: application/fhir+json`. The resource must contain an `id` element having an identical value to the ID in the REST path of the request. On success, the response body contains a JSON-encoded representation of the updated resource, including the server-assigned version ID. Errors generated by the FHIR store contain a JSON-encoded `OperationOutcome` resource describing the reason for the error. If the request cannot be mapped to a valid API method on a FHIR store, a generic GCP error might be returned instead. In R5, the conditional update interaction If-None-Match is supported, including the wildcard behaviour. For samples that show how to call `update`, see [Updating a FHIR resource](https://cloud.google.com/healthcare/docs/how-tos/fhir-resources#updating_a_fhir_resource).",
+"description": "Updates the entire contents of a resource. Implements the FHIR standard update interaction ([DSTU2](https://hl7.org/fhir/DSTU2/http.html#update), [STU3](https://hl7.org/fhir/STU3/http.html#update), [R4](https://hl7.org/fhir/R4/http.html#update), [R5](https://hl7.org/fhir/R5/http.html#update)). If the specified resource does not exist and the FHIR store has enable_update_create set, creates the resource with the client-specified ID. 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. The request body must contain a JSON-encoded FHIR resource, and the request headers must contain `Content-Type: application/fhir+json`. The resource must contain an `id` element having an identical value to the ID in the REST path of the request. On success, the response body contains a JSON-encoded representation of the updated resource, including the server-assigned version ID. Errors generated by the FHIR store contain a JSON-encoded `OperationOutcome` resource describing the reason for the error. If the request cannot be mapped to a valid API method on a FHIR store, a generic GCP error might be returned instead. The conditional update interaction If-None-Match is supported, including the wildcard behaviour, as defined by the R5 spec. This functionality is supported in R4 and R5. For samples that show how to call `update`, see [Updating a FHIR resource](https://cloud.google.com/healthcare/docs/how-tos/fhir-resources#updating_a_fhir_resource).",
 "flatPath": "v1beta1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/fhirStores/{fhirStoresId}/fhir/{fhirId}/{fhirId1}",
 "httpMethod": "PUT",
 "id": "healthcare.projects.locations.datasets.fhirStores.fhir.update",
@@ -5588,7 +5588,7 @@
 }
 }
 },
-"revision": "20250609",
+"revision": "20250710",
 "rootUrl": "https://healthcare.googleapis.com/",
 "schemas": {
 "AccessDeterminationLogConfig": {
@@ -6780,6 +6780,17 @@
 },
 "type": "object"
 },
+"DicomNotificationConfig": {
+"description": "Contains the configuration for DICOM notifications.",
+"id": "DicomNotificationConfig",
+"properties": {
+"pubsubTopic": {
+"description": "Required. 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. * `PubsubMessage.Attributes` contains the following attributes: * `action`: The name of the endpoint that generated the notification. Possible values are `StoreInstances`, `SetBlobSettings`, `ImportDicomData`, etc. * `lastUpdatedTime`: The latest timestamp when the DICOM instance was updated. * `storeName`: The resource name of the DICOM store, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`. * `studyInstanceUID`: The study UID of the DICOM instance that was changed. * `seriesInstanceUID`: The series UID of the DICOM instance that was changed. * `sopInstanceUID`: The instance UID of the DICOM instance that was changed. * `versionId`: The version ID of the DICOM instance that was changed. * `modality`: The modality tag of the DICOM instance that was changed. * `previousStorageClass`: The storage class where the DICOM instance was previously stored if the storage class was changed. * `storageClass`: The storage class where the DICOM instance is currently stored. 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 the `pubsub.topics.publish` permission (which is typically included in `roles/pubsub.publisher` role) 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"
+}
+},
+"type": "object"
+},
 "DicomStore": {
 "description": "Represents a DICOM store.",
 "id": "DicomStore",
@@ -6799,6 +6810,13 @@
 "$ref": "NotificationConfig",
 "description": "Notification destination for new DICOM instances. Supplied by the client."
 },
+"notificationConfigs": {
+"description": "Optional. Specifies where and whether to send notifications upon changes to a DICOM store.",
+"items": {
+"$ref": "DicomNotificationConfig"
+},
+"type": "array"
+},
 "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": {

googleapiclient/discovery_cache/documents/homegraph.v1.json

@@ -216,7 +216,7 @@
 }
 }
 },
-"revision": "20250410",
+"revision": "20250716",
 "rootUrl": "https://homegraph.googleapis.com/",
 "schemas": {
 "AgentDeviceId": {
@@ -349,7 +349,7 @@
 "type": "array"
 },
 "name": {
-"description": "Primary name of the device, generally provided by the user.",
+"description": "Primary name of the device, generally provided by the user. Names will be truncated if over the 60 Unicode code point (character) limit and no errors will be thrown. Developers are responsible for handling long names.",
 "type": "string"
 },
 "nicknames": {