feat: Automated regeneration of Dialogflow client (#12624)

Auto-created at 2024-11-27 13:20:09 +0000 using the toys pull request generator.
googleapis · Nov 27, 2024 · 9457c42 · 9457c42
1 parent 60b1121
commit 9457c42
Show file tree

Hide file tree

Showing 9 changed files with 9 additions and 9 deletions.
diff --git a/clients/dialogflow/lib/google_api/dialogflow/v3/metadata.ex b/clients/dialogflow/lib/google_api/dialogflow/v3/metadata.ex
@@ -20,7 +20,7 @@ defmodule GoogleApi.Dialogflow.V3 do
   API client metadata for GoogleApi.Dialogflow.V3.
   """
 
-  @discovery_revision "20241025"
+  @discovery_revision "20241119"
 
   def discovery_revision(), do: @discovery_revision
 end
diff --git a/...gflow/lib/google_api/dialogflow/v3/model/google_cloud_dialogflow_cx_v3_barge_in_config.ex b/...gflow/lib/google_api/dialogflow/v3/model/google_cloud_dialogflow_cx_v3_barge_in_config.ex
@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.Dialogflow.V3.Model.GoogleCloudDialogflowCxV3BargeInConfig do
   @moduledoc """
-  Configuration of the barge-in behavior. Barge-in instructs the API to return a detected utterance at a proper time while the client is playing back the response audio from a previous request. When the client sees the utterance, it should stop the playback and immediately get ready for receiving the responses for the current request. The barge-in handling requires the client to start streaming audio input as soon as it starts playing back the audio from the previous response. The playback is modeled into two phases: * No barge-in phase: which goes first and during which speech detection should not be carried out. * Barge-in phase: which follows the no barge-in phase and during which the API starts speech detection and may inform the client that an utterance has been detected. Note that no-speech event is not expected in this phase. The client provides this configuration in terms of the durations of those two phases. The durations are measured in terms of the audio length from the the start of the input audio. No-speech event is a response with END_OF_UTTERANCE without any transcript following up.
+  Configuration of the barge-in behavior. Barge-in instructs the API to return a detected utterance at a proper time while the client is playing back the response audio from a previous request. When the client sees the utterance, it should stop the playback and immediately get ready for receiving the responses for the current request. The barge-in handling requires the client to start streaming audio input as soon as it starts playing back the audio from the previous response. The playback is modeled into two phases: * No barge-in phase: which goes first and during which speech detection should not be carried out. * Barge-in phase: which follows the no barge-in phase and during which the API starts speech detection and may inform the client that an utterance has been detected. Note that no-speech event is not expected in this phase. The client provides this configuration in terms of the durations of those two phases. The durations are measured in terms of the audio length from the start of the input audio. No-speech event is a response with END_OF_UTTERANCE without any transcript following up.
 
   ## Attributes
 

diff --git a/.../lib/google_api/dialogflow/v3/model/google_cloud_dialogflow_cx_v3beta1_barge_in_config.ex b/.../lib/google_api/dialogflow/v3/model/google_cloud_dialogflow_cx_v3beta1_barge_in_config.ex
@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.Dialogflow.V3.Model.GoogleCloudDialogflowCxV3beta1BargeInConfig do
   @moduledoc """
-  Configuration of the barge-in behavior. Barge-in instructs the API to return a detected utterance at a proper time while the client is playing back the response audio from a previous request. When the client sees the utterance, it should stop the playback and immediately get ready for receiving the responses for the current request. The barge-in handling requires the client to start streaming audio input as soon as it starts playing back the audio from the previous response. The playback is modeled into two phases: * No barge-in phase: which goes first and during which speech detection should not be carried out. * Barge-in phase: which follows the no barge-in phase and during which the API starts speech detection and may inform the client that an utterance has been detected. Note that no-speech event is not expected in this phase. The client provides this configuration in terms of the durations of those two phases. The durations are measured in terms of the audio length from the the start of the input audio. No-speech event is a response with END_OF_UTTERANCE without any transcript following up.
+  Configuration of the barge-in behavior. Barge-in instructs the API to return a detected utterance at a proper time while the client is playing back the response audio from a previous request. When the client sees the utterance, it should stop the playback and immediately get ready for receiving the responses for the current request. The barge-in handling requires the client to start streaming audio input as soon as it starts playing back the audio from the previous response. The playback is modeled into two phases: * No barge-in phase: which goes first and during which speech detection should not be carried out. * Barge-in phase: which follows the no barge-in phase and during which the API starts speech detection and may inform the client that an utterance has been detected. Note that no-speech event is not expected in this phase. The client provides this configuration in terms of the durations of those two phases. The durations are measured in terms of the audio length from the start of the input audio. No-speech event is a response with END_OF_UTTERANCE without any transcript following up.
 
   ## Attributes
 

diff --git a/...v3/model/google_cloud_dialogflow_v2_clear_suggestion_feature_config_operation_metadata.ex b/...v3/model/google_cloud_dialogflow_v2_clear_suggestion_feature_config_operation_metadata.ex
@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.Dialogflow.V3.Model.GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata do
   @moduledoc """
-  Metadata for a ConversationProfile.ClearSuggestionFeatureConfig operation.
+  Metadata for a ConversationProfiles.ClearSuggestionFeatureConfig operation.
 
   ## Attributes
 

diff --git a/...low/v3/model/google_cloud_dialogflow_v2_create_conversation_dataset_operation_metadata.ex b/...low/v3/model/google_cloud_dialogflow_v2_create_conversation_dataset_operation_metadata.ex
@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.Dialogflow.V3.Model.GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata do
   @moduledoc """
-  Metadata for ConversationDatasets.
+  Metadata for CreateConversationDataset.
 
   ## Attributes
 

diff --git a/...low/v3/model/google_cloud_dialogflow_v2_delete_conversation_dataset_operation_metadata.ex b/...low/v3/model/google_cloud_dialogflow_v2_delete_conversation_dataset_operation_metadata.ex
@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.Dialogflow.V3.Model.GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata do
   @moduledoc """
-  Metadata for ConversationDatasets.
+  Metadata for DeleteConversationDataset.
 
   ## Attributes
 

diff --git a/...ib/google_api/dialogflow/v3/model/google_cloud_dialogflow_v2_sentiment_analysis_result.ex b/...ib/google_api/dialogflow/v3/model/google_cloud_dialogflow_v2_sentiment_analysis_result.ex
@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.Dialogflow.V3.Model.GoogleCloudDialogflowV2SentimentAnalysisResult do
   @moduledoc """
-  The result of sentiment analysis. Sentiment analysis inspects user input and identifies the prevailing subjective opinion, especially to determine a user's attitude as positive, negative, or neutral. For Participants.DetectIntent, it needs to be configured in DetectIntentRequest.query_params. For Participants.StreamingDetectIntent, it needs to be configured in StreamingDetectIntentRequest.query_params. And for Participants.AnalyzeContent and Participants.StreamingAnalyzeContent, it needs to be configured in ConversationProfile.human_agent_assistant_config
+  The result of sentiment analysis. Sentiment analysis inspects user input and identifies the prevailing subjective opinion, especially to determine a user's attitude as positive, negative, or neutral. For DetectIntent, it needs to be configured in DetectIntentRequest.query_params. For StreamingDetectIntent, it needs to be configured in StreamingDetectIntentRequest.query_params. And for Participants.AnalyzeContent and Participants.StreamingAnalyzeContent, it needs to be configured in ConversationProfile.human_agent_assistant_config
 
   ## Attributes
 

diff --git a/...w/v3/model/google_cloud_dialogflow_v2_set_suggestion_feature_config_operation_metadata.ex b/...w/v3/model/google_cloud_dialogflow_v2_set_suggestion_feature_config_operation_metadata.ex
@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.Dialogflow.V3.Model.GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata do
   @moduledoc """
-  Metadata for a ConversationProfile.SetSuggestionFeatureConfig operation.
+  Metadata for a ConversationProfiles.SetSuggestionFeatureConfig operation.
 
   ## Attributes
 

diff --git a/clients/dialogflow/mix.exs b/clients/dialogflow/mix.exs
@@ -18,7 +18,7 @@
 defmodule GoogleApi.Dialogflow.Mixfile do
   use Mix.Project
 
-  @version "0.88.1"
+  @version "0.88.2"
 
   def project() do
     [