google-cloud-discovery_engine-v1 2.3.0 → 2.4.0

data/lib/google/cloud/discovery_engine/v1/identity_mapping_store_service/rest/client.rb

@@ -228,13 +228,13 @@ module Google
               #     Resource name of the CmekConfig to use for protecting this Identity
               #     Mapping Store.
               #
-              #     Note: The following fields are mutually exclusive: `cmek_config_name`, `disable_cmek`. If a field in that set is populated, all other fields in the set will automatically be cleared.
+              #     Note: The following parameters are mutually exclusive: `cmek_config_name`, `disable_cmek`. At most one of these parameters can be set. If more than one is set, only one will be used, and it is not defined which one.
               #   @param disable_cmek [::Boolean]
               #     Identity Mapping Store without CMEK protections. If a default CmekConfig
               #     is set for the project, setting this field will override the default
               #     CmekConfig as well.
               #
-              #     Note: The following fields are mutually exclusive: `disable_cmek`, `cmek_config_name`. If a field in that set is populated, all other fields in the set will automatically be cleared.
+              #     Note: The following parameters are mutually exclusive: `disable_cmek`, `cmek_config_name`. At most one of these parameters can be set. If more than one is set, only one will be used, and it is not defined which one.
               #   @param parent [::String]
               #     Required. The parent collection resource name, such as
               #     `projects/{project}/locations/{location}`.

data/lib/google/cloud/discovery_engine/v1/rest.rb

@@ -16,10 +16,11 @@
 
 # Auto-generated by gapic-generator-ruby. DO NOT EDIT!
 
+require "google/cloud/discovery_engine/v1/search_service/rest"
+require "google/cloud/discovery_engine/v1/assistant_service/rest"
 require "google/cloud/discovery_engine/v1/cmek_config_service/rest"
 require "google/cloud/discovery_engine/v1/completion_service/rest"
 require "google/cloud/discovery_engine/v1/control_service/rest"
-require "google/cloud/discovery_engine/v1/search_service/rest"
 require "google/cloud/discovery_engine/v1/conversational_search_service/rest"
 require "google/cloud/discovery_engine/v1/data_store_service/rest"
 require "google/cloud/discovery_engine/v1/document_service/rest"
@@ -32,6 +33,7 @@ require "google/cloud/discovery_engine/v1/recommendation_service/rest"
 require "google/cloud/discovery_engine/v1/schema_service/rest"
 require "google/cloud/discovery_engine/v1/search_tuning_service/rest"
 require "google/cloud/discovery_engine/v1/serving_config_service/rest"
+require "google/cloud/discovery_engine/v1/session_service/rest"
 require "google/cloud/discovery_engine/v1/site_search_engine_service/rest"
 require "google/cloud/discovery_engine/v1/user_event_service/rest"
 require "google/cloud/discovery_engine/v1/user_license_service/rest"
@@ -46,7 +48,7 @@ module Google
       # @example
       #
       #     require "google/cloud/discovery_engine/v1/rest"
-      #     client = ::Google::Cloud::DiscoveryEngine::V1::CmekConfigService::Rest::Client.new
+      #     client = ::Google::Cloud::DiscoveryEngine::V1::SearchService::Rest::Client.new
       #
       module V1
       end

data/lib/google/cloud/discovery_engine/v1/search_service/client.rb

@@ -415,22 +415,16 @@ module Google
             #     between /search API calls and /answer API calls.
             #
             #     Example #1 (multi-turn /search API calls):
-            #       1. Call /search API with the auto-session mode (see below).
-            #       2. Call /search API with the session ID generated in the first call.
-            #          Here, the previous search query gets considered in query
-            #          standing. I.e., if the first query is "How did Alphabet do in 2022?"
-            #          and the current query is "How about 2023?", the current query will
-            #          be interpreted as "How did Alphabet do in 2023?".
+            #       Call /search API with the session ID generated in the first call.
+            #       Here, the previous search query gets considered in query
+            #       standing. I.e., if the first query is "How did Alphabet do in 2022?"
+            #       and the current query is "How about 2023?", the current query will
+            #       be interpreted as "How did Alphabet do in 2023?".
             #
             #     Example #2 (coordination between /search API calls and /answer API calls):
-            #       1. Call /search API with the auto-session mode (see below).
-            #       2. Call /answer API with the session ID generated in the first call.
-            #          Here, the answer generation happens in the context of the search
-            #          results from the first search call.
-            #
-            #     Auto-session mode: when `projects/.../sessions/-` is used, a new session
-            #     gets automatically created. Otherwise, users can use the create-session API
-            #     to create a session manually.
+            #       Call /answer API with the session ID generated in the first call.
+            #       Here, the answer generation happens in the context of the search
+            #       results from the first search call.
             #
             #     Multi-turn Search feature is currently at private GA stage. Please use
             #     v1alpha or v1beta version instead before we launch this feature to public
@@ -743,22 +737,16 @@ module Google
             #     between /search API calls and /answer API calls.
             #
             #     Example #1 (multi-turn /search API calls):
-            #       1. Call /search API with the auto-session mode (see below).
-            #       2. Call /search API with the session ID generated in the first call.
-            #          Here, the previous search query gets considered in query
-            #          standing. I.e., if the first query is "How did Alphabet do in 2022?"
-            #          and the current query is "How about 2023?", the current query will
-            #          be interpreted as "How did Alphabet do in 2023?".
+            #       Call /search API with the session ID generated in the first call.
+            #       Here, the previous search query gets considered in query
+            #       standing. I.e., if the first query is "How did Alphabet do in 2022?"
+            #       and the current query is "How about 2023?", the current query will
+            #       be interpreted as "How did Alphabet do in 2023?".
             #
             #     Example #2 (coordination between /search API calls and /answer API calls):
-            #       1. Call /search API with the auto-session mode (see below).
-            #       2. Call /answer API with the session ID generated in the first call.
-            #          Here, the answer generation happens in the context of the search
-            #          results from the first search call.
-            #
-            #     Auto-session mode: when `projects/.../sessions/-` is used, a new session
-            #     gets automatically created. Otherwise, users can use the create-session API
-            #     to create a session manually.
+            #       Call /answer API with the session ID generated in the first call.
+            #       Here, the answer generation happens in the context of the search
+            #       results from the first search call.
             #
             #     Multi-turn Search feature is currently at private GA stage. Please use
             #     v1alpha or v1beta version instead before we launch this feature to public

data/lib/google/cloud/discovery_engine/v1/search_service/rest/client.rb

@@ -408,22 +408,16 @@ module Google
               #     between /search API calls and /answer API calls.
               #
               #     Example #1 (multi-turn /search API calls):
-              #       1. Call /search API with the auto-session mode (see below).
-              #       2. Call /search API with the session ID generated in the first call.
-              #          Here, the previous search query gets considered in query
-              #          standing. I.e., if the first query is "How did Alphabet do in 2022?"
-              #          and the current query is "How about 2023?", the current query will
-              #          be interpreted as "How did Alphabet do in 2023?".
+              #       Call /search API with the session ID generated in the first call.
+              #       Here, the previous search query gets considered in query
+              #       standing. I.e., if the first query is "How did Alphabet do in 2022?"
+              #       and the current query is "How about 2023?", the current query will
+              #       be interpreted as "How did Alphabet do in 2023?".
               #
               #     Example #2 (coordination between /search API calls and /answer API calls):
-              #       1. Call /search API with the auto-session mode (see below).
-              #       2. Call /answer API with the session ID generated in the first call.
-              #          Here, the answer generation happens in the context of the search
-              #          results from the first search call.
-              #
-              #     Auto-session mode: when `projects/.../sessions/-` is used, a new session
-              #     gets automatically created. Otherwise, users can use the create-session API
-              #     to create a session manually.
+              #       Call /answer API with the session ID generated in the first call.
+              #       Here, the answer generation happens in the context of the search
+              #       results from the first search call.
               #
               #     Multi-turn Search feature is currently at private GA stage. Please use
               #     v1alpha or v1beta version instead before we launch this feature to public
@@ -729,22 +723,16 @@ module Google
               #     between /search API calls and /answer API calls.
               #
               #     Example #1 (multi-turn /search API calls):
-              #       1. Call /search API with the auto-session mode (see below).
-              #       2. Call /search API with the session ID generated in the first call.
-              #          Here, the previous search query gets considered in query
-              #          standing. I.e., if the first query is "How did Alphabet do in 2022?"
-              #          and the current query is "How about 2023?", the current query will
-              #          be interpreted as "How did Alphabet do in 2023?".
+              #       Call /search API with the session ID generated in the first call.
+              #       Here, the previous search query gets considered in query
+              #       standing. I.e., if the first query is "How did Alphabet do in 2022?"
+              #       and the current query is "How about 2023?", the current query will
+              #       be interpreted as "How did Alphabet do in 2023?".
               #
               #     Example #2 (coordination between /search API calls and /answer API calls):
-              #       1. Call /search API with the auto-session mode (see below).
-              #       2. Call /answer API with the session ID generated in the first call.
-              #          Here, the answer generation happens in the context of the search
-              #          results from the first search call.
-              #
-              #     Auto-session mode: when `projects/.../sessions/-` is used, a new session
-              #     gets automatically created. Otherwise, users can use the create-session API
-              #     to create a session manually.
+              #       Call /answer API with the session ID generated in the first call.
+              #       Here, the answer generation happens in the context of the search
+              #       results from the first search call.
               #
               #     Multi-turn Search feature is currently at private GA stage. Please use
               #     v1alpha or v1beta version instead before we launch this feature to public