feat(discoveryengine): update the api

#### discoveryengine:v1

The following keys were deleted:
- schemas.GoogleCloudDiscoveryengineV1alphaExportUserEventsMetadata (Total Keys: 6)
- schemas.GoogleCloudDiscoveryengineV1alphaExportUserEventsResponse (Total Keys: 3)

The following keys were added:
- schemas.GoogleCloudDiscoveryengineV1DocumentInfo.properties.joined (Total Keys: 2)
- schemas.GoogleCloudDiscoveryengineV1FhirStoreSource.properties.resourceTypes (Total Keys: 2)

#### discoveryengine:v1alpha

The following keys were deleted:
- schemas.GoogleCloudDiscoveryengineV1alphaExportUserEventsMetadata (Total Keys: 6)
- schemas.GoogleCloudDiscoveryengineV1alphaExportUserEventsResponse (Total Keys: 3)

The following keys were added:
- schemas.GoogleCloudDiscoveryengineV1alphaDocumentInfo.properties.joined (Total Keys: 2)
- schemas.GoogleCloudDiscoveryengineV1alphaFhirStoreSource.properties.resourceTypes (Total Keys: 2)
- schemas.GoogleCloudDiscoveryengineV1alphaSearchResponseNaturalLanguageQueryUnderstandingInfoStructuredExtractedFilterGeolocationConstraint.properties.latitude (Total Keys: 2)
- schemas.GoogleCloudDiscoveryengineV1alphaSearchResponseNaturalLanguageQueryUnderstandingInfoStructuredExtractedFilterGeolocationConstraint.properties.longitude (Total Keys: 2)

#### discoveryengine:v1beta

The following keys were deleted:
- schemas.GoogleCloudDiscoveryengineV1alphaExportUserEventsMetadata (Total Keys: 6)
- schemas.GoogleCloudDiscoveryengineV1alphaExportUserEventsResponse (Total Keys: 3)

The following keys were added:
- schemas.GoogleCloudDiscoveryengineV1betaDocumentInfo.properties.joined (Total Keys: 2)
- schemas.GoogleCloudDiscoveryengineV1betaFhirStoreSource.properties.resourceTypes (Total Keys: 2)
- schemas.GoogleCloudDiscoveryengineV1betaSearchResponseNaturalLanguageQueryUnderstandingInfoStructuredExtractedFilterGeolocationConstraint.properties.latitude (Total Keys: 2)
- schemas.GoogleCloudDiscoveryengineV1betaSearchResponseNaturalLanguageQueryUnderstandingInfoStructuredExtractedFilterGeolocationConstraint.properties.longitude (Total Keys: 2)

Author: yoshi-automation

docs/dyn/discoveryengine_v1.projects.locations.collections.dataStores.branches.documents.html

@@ -287,6 +287,9 @@ <h3>Method Details</h3>
   &quot;fhirStoreSource&quot;: { # Cloud FhirStore source import data from. # FhirStore input source.
     &quot;fhirStore&quot;: &quot;A String&quot;, # Required. The full resource name of the FHIR store to import data from, in the format of `projects/{project}/locations/{location}/datasets/{dataset}/fhirStores/{fhir_store}`.
     &quot;gcsStagingDir&quot;: &quot;A String&quot;, # Intermediate Cloud Storage directory used for the import with a length limit of 2,000 characters. Can be specified if one wants to have the FhirStore export to a specific Cloud Storage directory.
+    &quot;resourceTypes&quot;: [ # The FHIR resource types to import. The resource types should be a subset of all [supported FHIR resource types](https://cloud.google.com/generative-ai-app-builder/docs/fhir-schema-reference#resource-level-specification). Default to all supported FHIR resource types if empty.
+      &quot;A String&quot;,
+    ],
   },
   &quot;firestoreSource&quot;: { # Firestore source import data from. # Firestore input source.
     &quot;collectionId&quot;: &quot;A String&quot;, # Required. The Firestore collection (or entity) to copy the data from with a length limit of 1,500 characters.

docs/dyn/discoveryengine_v1.projects.locations.collections.dataStores.html

@@ -232,7 +232,7 @@ <h3>Method Details</h3>
       },
     },
     &quot;name&quot;: &quot;A String&quot;, # The full resource name of the Document Processing Config. Format: `projects/*/locations/*/collections/*/dataStores/*/documentProcessingConfig`.
-    &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported.
+    &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported. * `xlsx`: Override parsing config for XLSX files, only digital parsing and layout parsing are supported.
       &quot;a_key&quot;: { # Related configurations applied to a specific type of document parser.
         &quot;digitalParsingConfig&quot;: { # The digital parsing configurations for documents. # Configurations applied to digital parser.
         },
@@ -367,7 +367,7 @@ <h3>Method Details</h3>
       },
     },
     &quot;name&quot;: &quot;A String&quot;, # The full resource name of the Document Processing Config. Format: `projects/*/locations/*/collections/*/dataStores/*/documentProcessingConfig`.
-    &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported.
+    &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported. * `xlsx`: Override parsing config for XLSX files, only digital parsing and layout parsing are supported.
       &quot;a_key&quot;: { # Related configurations applied to a specific type of document parser.
         &quot;digitalParsingConfig&quot;: { # The digital parsing configurations for documents. # Configurations applied to digital parser.
         },
@@ -460,7 +460,7 @@ <h3>Method Details</h3>
           },
         },
         &quot;name&quot;: &quot;A String&quot;, # The full resource name of the Document Processing Config. Format: `projects/*/locations/*/collections/*/dataStores/*/documentProcessingConfig`.
-        &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported.
+        &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported. * `xlsx`: Override parsing config for XLSX files, only digital parsing and layout parsing are supported.
           &quot;a_key&quot;: { # Related configurations applied to a specific type of document parser.
             &quot;digitalParsingConfig&quot;: { # The digital parsing configurations for documents. # Configurations applied to digital parser.
             },
@@ -541,7 +541,7 @@ <h3>Method Details</h3>
       },
     },
     &quot;name&quot;: &quot;A String&quot;, # The full resource name of the Document Processing Config. Format: `projects/*/locations/*/collections/*/dataStores/*/documentProcessingConfig`.
-    &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported.
+    &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported. * `xlsx`: Override parsing config for XLSX files, only digital parsing and layout parsing are supported.
       &quot;a_key&quot;: { # Related configurations applied to a specific type of document parser.
         &quot;digitalParsingConfig&quot;: { # The digital parsing configurations for documents. # Configurations applied to digital parser.
         },
@@ -604,7 +604,7 @@ <h3>Method Details</h3>
       },
     },
     &quot;name&quot;: &quot;A String&quot;, # The full resource name of the Document Processing Config. Format: `projects/*/locations/*/collections/*/dataStores/*/documentProcessingConfig`.
-    &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported.
+    &quot;parsingConfigOverrides&quot;: { # Map from file type to override the default parsing configuration based on the file type. Supported keys: * `pdf`: Override parsing config for PDF files, either digital parsing, ocr parsing or layout parsing is supported. * `html`: Override parsing config for HTML files, only digital parsing and layout parsing are supported. * `docx`: Override parsing config for DOCX files, only digital parsing and layout parsing are supported. * `pptx`: Override parsing config for PPTX files, only digital parsing and layout parsing are supported. * `xlsx`: Override parsing config for XLSX files, only digital parsing and layout parsing are supported.
       &quot;a_key&quot;: { # Related configurations applied to a specific type of document parser.
         &quot;digitalParsingConfig&quot;: { # The digital parsing configurations for documents. # Configurations applied to digital parser.
         },

docs/dyn/discoveryengine_v1.projects.locations.collections.dataStores.servingConfigs.html

@@ -376,6 +376,7 @@ <h3>Method Details</h3>
     &quot;documents&quot;: [ # List of Documents associated with this user event. This field is optional except for the following event types: * `view-item` * `add-to-cart` * `purchase` * `media-play` * `media-complete` In a `search` event, this field represents the documents returned to the end user on the current page (the end user may have not finished browsing the whole page yet). When a new page is returned to the end user, after pagination/filtering/ordering even for the same query, a new `search` event with different UserEvent.documents is desired.
       { # Detailed document information associated with a user event.
         &quot;id&quot;: &quot;A String&quot;, # The Document resource ID.
+        &quot;joined&quot;: True or False, # Output only. Whether the referenced Document can be found in the data store.
         &quot;name&quot;: &quot;A String&quot;, # The Document resource full name, of the form: `projects/{project_id}/locations/{location}/collections/{collection_id}/dataStores/{data_store_id}/branches/{branch_id}/documents/{document_id}`
         &quot;promotionIds&quot;: [ # The promotion IDs associated with this Document. Currently, this field is restricted to at most one ID.
           &quot;A String&quot;,

docs/dyn/discoveryengine_v1.projects.locations.collections.dataStores.userEvents.html

@@ -177,6 +177,7 @@ <h3>Method Details</h3>
         &quot;documents&quot;: [ # List of Documents associated with this user event. This field is optional except for the following event types: * `view-item` * `add-to-cart` * `purchase` * `media-play` * `media-complete` In a `search` event, this field represents the documents returned to the end user on the current page (the end user may have not finished browsing the whole page yet). When a new page is returned to the end user, after pagination/filtering/ordering even for the same query, a new `search` event with different UserEvent.documents is desired.
           { # Detailed document information associated with a user event.
             &quot;id&quot;: &quot;A String&quot;, # The Document resource ID.
+            &quot;joined&quot;: True or False, # Output only. Whether the referenced Document can be found in the data store.
             &quot;name&quot;: &quot;A String&quot;, # The Document resource full name, of the form: `projects/{project_id}/locations/{location}/collections/{collection_id}/dataStores/{data_store_id}/branches/{branch_id}/documents/{document_id}`
             &quot;promotionIds&quot;: [ # The promotion IDs associated with this Document. Currently, this field is restricted to at most one ID.
               &quot;A String&quot;,
@@ -337,6 +338,7 @@ <h3>Method Details</h3>
   &quot;documents&quot;: [ # List of Documents associated with this user event. This field is optional except for the following event types: * `view-item` * `add-to-cart` * `purchase` * `media-play` * `media-complete` In a `search` event, this field represents the documents returned to the end user on the current page (the end user may have not finished browsing the whole page yet). When a new page is returned to the end user, after pagination/filtering/ordering even for the same query, a new `search` event with different UserEvent.documents is desired.
     { # Detailed document information associated with a user event.
       &quot;id&quot;: &quot;A String&quot;, # The Document resource ID.
+      &quot;joined&quot;: True or False, # Output only. Whether the referenced Document can be found in the data store.
       &quot;name&quot;: &quot;A String&quot;, # The Document resource full name, of the form: `projects/{project_id}/locations/{location}/collections/{collection_id}/dataStores/{data_store_id}/branches/{branch_id}/documents/{document_id}`
       &quot;promotionIds&quot;: [ # The promotion IDs associated with this Document. Currently, this field is restricted to at most one ID.
         &quot;A String&quot;,
@@ -422,6 +424,7 @@ <h3>Method Details</h3>
   &quot;documents&quot;: [ # List of Documents associated with this user event. This field is optional except for the following event types: * `view-item` * `add-to-cart` * `purchase` * `media-play` * `media-complete` In a `search` event, this field represents the documents returned to the end user on the current page (the end user may have not finished browsing the whole page yet). When a new page is returned to the end user, after pagination/filtering/ordering even for the same query, a new `search` event with different UserEvent.documents is desired.
     { # Detailed document information associated with a user event.
       &quot;id&quot;: &quot;A String&quot;, # The Document resource ID.
+      &quot;joined&quot;: True or False, # Output only. Whether the referenced Document can be found in the data store.
       &quot;name&quot;: &quot;A String&quot;, # The Document resource full name, of the form: `projects/{project_id}/locations/{location}/collections/{collection_id}/dataStores/{data_store_id}/branches/{branch_id}/documents/{document_id}`
       &quot;promotionIds&quot;: [ # The promotion IDs associated with this Document. Currently, this field is restricted to at most one ID.
         &quot;A String&quot;,

docs/dyn/discoveryengine_v1.projects.locations.collections.engines.servingConfigs.html

@@ -376,6 +376,7 @@ <h3>Method Details</h3>
     &quot;documents&quot;: [ # List of Documents associated with this user event. This field is optional except for the following event types: * `view-item` * `add-to-cart` * `purchase` * `media-play` * `media-complete` In a `search` event, this field represents the documents returned to the end user on the current page (the end user may have not finished browsing the whole page yet). When a new page is returned to the end user, after pagination/filtering/ordering even for the same query, a new `search` event with different UserEvent.documents is desired.
       { # Detailed document information associated with a user event.
         &quot;id&quot;: &quot;A String&quot;, # The Document resource ID.
+        &quot;joined&quot;: True or False, # Output only. Whether the referenced Document can be found in the data store.
         &quot;name&quot;: &quot;A String&quot;, # The Document resource full name, of the form: `projects/{project_id}/locations/{location}/collections/{collection_id}/dataStores/{data_store_id}/branches/{branch_id}/documents/{document_id}`
         &quot;promotionIds&quot;: [ # The promotion IDs associated with this Document. Currently, this field is restricted to at most one ID.
           &quot;A String&quot;,

docs/dyn/discoveryengine_v1.projects.locations.dataStores.branches.documents.html

@@ -287,6 +287,9 @@ <h3>Method Details</h3>
   &quot;fhirStoreSource&quot;: { # Cloud FhirStore source import data from. # FhirStore input source.
     &quot;fhirStore&quot;: &quot;A String&quot;, # Required. The full resource name of the FHIR store to import data from, in the format of `projects/{project}/locations/{location}/datasets/{dataset}/fhirStores/{fhir_store}`.
     &quot;gcsStagingDir&quot;: &quot;A String&quot;, # Intermediate Cloud Storage directory used for the import with a length limit of 2,000 characters. Can be specified if one wants to have the FhirStore export to a specific Cloud Storage directory.
+    &quot;resourceTypes&quot;: [ # The FHIR resource types to import. The resource types should be a subset of all [supported FHIR resource types](https://cloud.google.com/generative-ai-app-builder/docs/fhir-schema-reference#resource-level-specification). Default to all supported FHIR resource types if empty.
+      &quot;A String&quot;,
+    ],
   },
   &quot;firestoreSource&quot;: { # Firestore source import data from. # Firestore input source.
     &quot;collectionId&quot;: &quot;A String&quot;, # Required. The Firestore collection (or entity) to copy the data from with a length limit of 1,500 characters.