google-api-python-client 2.153.0__py2.py3-none-any.whl → 2.155.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/deploymentmanager.v2beta.json

@@ -1636,7 +1636,7 @@
 }
 }
 },
-"revision": "20241031",
+"revision": "20241122",
 "rootUrl": "https://deploymentmanager.googleapis.com/",
 "schemas": {
 "AsyncOptions": {
@@ -2593,11 +2593,12 @@
 "LIST_OVERHEAD_QUOTA_EXCEED",
 "QUOTA_INFO_UNAVAILABLE",
 "RESOURCE_USES_GLOBAL_DNS",
-"RESERVED_ENTRY_134",
+"RATE_LIMIT_EXCEEDED",
 "RESERVED_ENTRY_135",
 "RESERVED_ENTRY_136",
 "RESERVED_ENTRY_139",
-"RESERVED_ENTRY_141"
+"RESERVED_ENTRY_141",
+"RESERVED_ENTRY_142"
 ],
 "enumDeprecated": [
 false,
@@ -2638,6 +2639,7 @@ false,
 false,
 false,
 false,
+false,
 false
 ],
 "enumDescriptions": [
@@ -2675,6 +2677,7 @@ false
 "Resource can't be retrieved due to list overhead quota exceed which captures the amount of resources filtered out by user-defined list filter.",
 "Quota information is not available to client requests (e.g: regions.list).",
 "Indicates that a VM is using global DNS. Can also be used to indicate that a resource has attributes that could result in the creation of a VM that uses global DNS.",
+"Resource can't be retrieved due to api quota exceeded.",
 "Reserved entries for quickly adding new warnings without breaking dependent clients.",
 "",
 "",
@@ -2955,11 +2958,12 @@ false
 "LIST_OVERHEAD_QUOTA_EXCEED",
 "QUOTA_INFO_UNAVAILABLE",
 "RESOURCE_USES_GLOBAL_DNS",
-"RESERVED_ENTRY_134",
+"RATE_LIMIT_EXCEEDED",
 "RESERVED_ENTRY_135",
 "RESERVED_ENTRY_136",
 "RESERVED_ENTRY_139",
-"RESERVED_ENTRY_141"
+"RESERVED_ENTRY_141",
+"RESERVED_ENTRY_142"
 ],
 "enumDeprecated": [
 false,
@@ -3000,6 +3004,7 @@ false,
 false,
 false,
 false,
+false,
 false
 ],
 "enumDescriptions": [
@@ -3037,6 +3042,7 @@ false
 "Resource can't be retrieved due to list overhead quota exceed which captures the amount of resources filtered out by user-defined list filter.",
 "Quota information is not available to client requests (e.g: regions.list).",
 "Indicates that a VM is using global DNS. Can also be used to indicate that a resource has attributes that could result in the creation of a VM that uses global DNS.",
+"Resource can't be retrieved due to api quota exceeded.",
 "Reserved entries for quickly adding new warnings without breaking dependent clients.",
 "",
 "",
@@ -3241,11 +3247,12 @@ false
 "LIST_OVERHEAD_QUOTA_EXCEED",
 "QUOTA_INFO_UNAVAILABLE",
 "RESOURCE_USES_GLOBAL_DNS",
-"RESERVED_ENTRY_134",
+"RATE_LIMIT_EXCEEDED",
 "RESERVED_ENTRY_135",
 "RESERVED_ENTRY_136",
 "RESERVED_ENTRY_139",
-"RESERVED_ENTRY_141"
+"RESERVED_ENTRY_141",
+"RESERVED_ENTRY_142"
 ],
 "enumDeprecated": [
 false,
@@ -3286,6 +3293,7 @@ false,
 false,
 false,
 false,
+false,
 false
 ],
 "enumDescriptions": [
@@ -3323,6 +3331,7 @@ false
 "Resource can't be retrieved due to list overhead quota exceed which captures the amount of resources filtered out by user-defined list filter.",
 "Quota information is not available to client requests (e.g: regions.list).",
 "Indicates that a VM is using global DNS. Can also be used to indicate that a resource has attributes that could result in the creation of a VM that uses global DNS.",
+"Resource can't be retrieved due to api quota exceeded.",
 "Reserved entries for quickly adding new warnings without breaking dependent clients.",
 "",
 "",

googleapiclient/discovery_cache/documents/developerconnect.v1.json

@@ -967,7 +967,7 @@
 }
 }
 },
-"revision": "20241023",
+"revision": "20241107",
 "rootUrl": "https://developerconnect.googleapis.com/",
 "schemas": {
 "CancelOperationRequest": {
@@ -1676,7 +1676,7 @@
 "type": "string"
 },
 "requestedCancellation": {
-"description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have been cancelled successfully have Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
+"description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have been cancelled successfully have google.longrunning.Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
 "readOnly": true,
 "type": "boolean"
 },

googleapiclient/discovery_cache/documents/dialogflow.v2.json

@@ -3060,7 +3060,7 @@
 ]
 },
 "create": {
-"description": "Creates a conversation profile in the specified project. ConversationProfile.CreateTime and ConversationProfile.UpdateTime aren't populated in the response. You can retrieve them via GetConversationProfile API.",
+"description": "Creates a conversation profile in the specified project. ConversationProfile.create_time and ConversationProfile.update_time aren't populated in the response. You can retrieve them via GetConversationProfile API.",
 "flatPath": "v2/projects/{projectsId}/conversationProfiles",
 "httpMethod": "POST",
 "id": "dialogflow.projects.conversationProfiles.create",
@@ -3178,7 +3178,7 @@
 ]
 },
 "patch": {
-"description": "Updates the specified conversation profile. ConversationProfile.CreateTime and ConversationProfile.UpdateTime aren't populated in the response. You can retrieve them via GetConversationProfile API.",
+"description": "Updates the specified conversation profile. ConversationProfile.create_time and ConversationProfile.update_time aren't populated in the response. You can retrieve them via GetConversationProfile API.",
 "flatPath": "v2/projects/{projectsId}/conversationProfiles/{conversationProfilesId}",
 "httpMethod": "PATCH",
 "id": "dialogflow.projects.conversationProfiles.patch",
@@ -7033,7 +7033,7 @@
 ]
 },
 "create": {
-"description": "Creates a conversation profile in the specified project. ConversationProfile.CreateTime and ConversationProfile.UpdateTime aren't populated in the response. You can retrieve them via GetConversationProfile API.",
+"description": "Creates a conversation profile in the specified project. ConversationProfile.create_time and ConversationProfile.update_time aren't populated in the response. You can retrieve them via GetConversationProfile API.",
 "flatPath": "v2/projects/{projectsId}/locations/{locationsId}/conversationProfiles",
 "httpMethod": "POST",
 "id": "dialogflow.projects.locations.conversationProfiles.create",
@@ -7151,7 +7151,7 @@
 ]
 },
 "patch": {
-"description": "Updates the specified conversation profile. ConversationProfile.CreateTime and ConversationProfile.UpdateTime aren't populated in the response. You can retrieve them via GetConversationProfile API.",
+"description": "Updates the specified conversation profile. ConversationProfile.create_time and ConversationProfile.update_time aren't populated in the response. You can retrieve them via GetConversationProfile API.",
 "flatPath": "v2/projects/{projectsId}/locations/{locationsId}/conversationProfiles/{conversationProfilesId}",
 "httpMethod": "PATCH",
 "id": "dialogflow.projects.locations.conversationProfiles.patch",
@@ -8714,7 +8714,7 @@
 }
 }
 },
-"revision": "20241019",
+"revision": "20241119",
 "rootUrl": "https://dialogflow.googleapis.com/",
 "schemas": {
 "GoogleCloudDialogflowCxV3AdvancedSettings": {
@@ -8834,7 +8834,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3BargeInConfig": {
-"description": "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.",
+"description": "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.",
 "id": "GoogleCloudDialogflowCxV3BargeInConfig",
 "properties": {
 "noBargeInDuration": {
@@ -11141,7 +11141,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3beta1BargeInConfig": {
-"description": "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.",
+"description": "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.",
 "id": "GoogleCloudDialogflowCxV3beta1BargeInConfig",
 "properties": {
 "noBargeInDuration": {
@@ -13680,7 +13680,7 @@ true
 "properties": {
 "automatedAgentReply": {
 "$ref": "GoogleCloudDialogflowV2AutomatedAgentReply",
-"description": "Only set if a Dialogflow automated agent has responded. Note that: AutomatedAgentReply.detect_intent_response.output_audio and AutomatedAgentReply.detect_intent_response.output_audio_config are always empty, use reply_audio instead."
+"description": "Only set if a Dialogflow automated agent has responded. Note that in AutomatedAgentReply.DetectIntentResponse, Sessions.DetectIntentResponse.output_audio and Sessions.DetectIntentResponse.output_audio_config are always empty, use reply_audio instead."
 },
 "dtmfParameters": {
 "$ref": "GoogleCloudDialogflowV2DtmfParameters",
@@ -13780,7 +13780,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2AnswerRecord": {
-"description": "Answer records are records to manage answer history and feedbacks for Dialogflow. Currently, answer record includes: - human agent assistant article suggestion - human agent assistant faq article It doesn't include: - `DetectIntent` intent matching - `DetectIntent` knowledge Answer records are not related to the conversation history in the Dialogflow Console. A Record is generated even when the end-user disables conversation history in the console. Records are created when there's a human agent assistant suggestion generated. A typical workflow for customers provide feedback to an answer is: 1. For human agent assistant, customers get suggestion via ListSuggestions API. Together with the answers, AnswerRecord.name are returned to the customers. 2. The customer uses the AnswerRecord.name to call the UpdateAnswerRecord method to send feedback about a specific answer that they believe is wrong.",
+"description": "Answer records are records to manage answer history and feedbacks for Dialogflow. Currently, answer record includes: - human agent assistant article suggestion - human agent assistant faq article It doesn't include: - `DetectIntent` intent matching - `DetectIntent` knowledge Answer records are not related to the conversation history in the Dialogflow Console. A Record is generated even when the end-user disables conversation history in the console. Records are created when there's a human agent assistant suggestion generated. A typical workflow for customers provide feedback to an answer is: 1. For human agent assistant, customers get suggestion via ListSuggestions API. Together with the answers, AnswerRecord.name are returned to the customers. 2. The customer uses the AnswerRecord.name to call the AnswerRecords.UpdateAnswerRecord method to send feedback about a specific answer that they believe is wrong.",
 "id": "GoogleCloudDialogflowV2AnswerRecord",
 "properties": {
 "agentAssistantRecord": {
@@ -14096,7 +14096,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata": {
-"description": "Metadata for a ConversationProfile.ClearSuggestionFeatureConfig operation.",
+"description": "Metadata for a ConversationProfiles.ClearSuggestionFeatureConfig operation.",
 "id": "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata",
 "properties": {
 "conversationProfile": {
@@ -14148,7 +14148,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigRequest": {
-"description": "The request message for ConversationProfiles.ClearFeature.",
+"description": "The request message for ConversationProfiles.ClearSuggestionFeatureConfig.",
 "id": "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigRequest",
 "properties": {
 "participantRole": {
@@ -14594,7 +14594,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata": {
-"description": "Metadata for ConversationDatasets.",
+"description": "Metadata for CreateConversationDataset.",
 "id": "GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata",
 "properties": {
 "conversationDataset": {
@@ -14694,7 +14694,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata": {
-"description": "Metadata for ConversationDatasets.",
+"description": "Metadata for DeleteConversationDataset.",
 "id": "GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata",
 "properties": {},
 "type": "object"
@@ -15293,7 +15293,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2FewShotExample": {
-"description": "Providing examples in the generator (i.e. building a few-shot generator) helps convey the desired format of the LLM response. NEXT_ID: 10",
+"description": "Providing examples in the generator (i.e. building a few-shot generator) helps convey the desired format of the LLM response.",
 "id": "GoogleCloudDialogflowV2FewShotExample",
 "properties": {
 "conversationContext": {
@@ -15513,7 +15513,7 @@ true
 "id": "GoogleCloudDialogflowV2GenerateStatelessSummaryResponse",
 "properties": {
 "contextSize": {
-"description": "Number of messages prior to and including last_conversation_message used to compile the suggestion. It may be smaller than the GenerateStatelessSummaryRequest.context_size field in the request if there weren't that many messages in the conversation.",
+"description": "Number of messages prior to and including latest_message used to compile the suggestion. It may be smaller than the GenerateStatelessSummaryRequest.max_context_size field in the request if there weren't that many messages in the conversation.",
 "format": "int32",
 "type": "integer"
 },
@@ -18347,7 +18347,7 @@ true
 "id": "GoogleCloudDialogflowV2SearchKnowledgeRequestSearchConfigBoostSpecs",
 "properties": {
 "dataStores": {
-"description": "Optional. Data Stores where the boosting configuration is applied. The full names of the referenced data stores. Formats: `projects/{project}/locations/{location}/collections/{collection}/dataStores/{data_store}` `projects/{project}/locations/{location}/dataStores/{data_store}",
+"description": "Optional. Data Stores where the boosting configuration is applied. The full names of the referenced data stores. Formats: `projects/{project}/locations/{location}/collections/{collection}/dataStores/{data_store}` `projects/{project}/locations/{location}/dataStores/{data_store}`",
 "items": {
 "type": "string"
 },
@@ -18522,7 +18522,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SentimentAnalysisResult": {
-"description": "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",
+"description": "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",
 "id": "GoogleCloudDialogflowV2SentimentAnalysisResult",
 "properties": {
 "queryTextSentiment": {
@@ -18565,7 +18565,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata": {
-"description": "Metadata for a ConversationProfile.SetSuggestionFeatureConfig operation.",
+"description": "Metadata for a ConversationProfiles.SetSuggestionFeatureConfig operation.",
 "id": "GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata",
 "properties": {
 "conversationProfile": {
@@ -18617,7 +18617,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SetSuggestionFeatureConfigRequest": {
-"description": "The request message for ConversationProfiles.SetSuggestionFeature.",
+"description": "The request message for ConversationProfiles.SetSuggestionFeatureConfig.",
 "id": "GoogleCloudDialogflowV2SetSuggestionFeatureConfigRequest",
 "properties": {
 "participantRole": {
@@ -18889,7 +18889,7 @@ true
 "id": "GoogleCloudDialogflowV2SuggestConversationSummaryResponse",
 "properties": {
 "contextSize": {
-"description": "Number of messages prior to and including last_conversation_message used to compile the suggestion. It may be smaller than the SuggestSummaryRequest.context_size field in the request if there weren't that many messages in the conversation.",
+"description": "Number of messages prior to and including latest_message used to compile the suggestion. It may be smaller than the SuggestConversationSummaryRequest.context_size field in the request if there weren't that many messages in the conversation.",
 "format": "int32",
 "type": "integer"
 },

googleapiclient/discovery_cache/documents/dialogflow.v2beta1.json

@@ -8239,7 +8239,7 @@
 }
 }
 },
-"revision": "20241025",
+"revision": "20241119",
 "rootUrl": "https://dialogflow.googleapis.com/",
 "schemas": {
 "GoogleCloudDialogflowCxV3AdvancedSettings": {
@@ -8359,7 +8359,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3BargeInConfig": {
-"description": "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.",
+"description": "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.",
 "id": "GoogleCloudDialogflowCxV3BargeInConfig",
 "properties": {
 "noBargeInDuration": {
@@ -10666,7 +10666,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3beta1BargeInConfig": {
-"description": "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.",
+"description": "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.",
 "id": "GoogleCloudDialogflowCxV3beta1BargeInConfig",
 "properties": {
 "noBargeInDuration": {
@@ -13016,7 +13016,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata": {
-"description": "Metadata for a ConversationProfile.ClearSuggestionFeatureConfig operation.",
+"description": "Metadata for a ConversationProfiles.ClearSuggestionFeatureConfig operation.",
 "id": "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata",
 "properties": {
 "conversationProfile": {
@@ -13208,7 +13208,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata": {
-"description": "Metadata for ConversationDatasets.",
+"description": "Metadata for CreateConversationDataset.",
 "id": "GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata",
 "properties": {
 "conversationDataset": {
@@ -13297,7 +13297,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata": {
-"description": "Metadata for ConversationDatasets.",
+"description": "Metadata for DeleteConversationDataset.",
 "id": "GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata",
 "properties": {},
 "type": "object"
@@ -14886,7 +14886,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SentimentAnalysisResult": {
-"description": "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",
+"description": "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",
 "id": "GoogleCloudDialogflowV2SentimentAnalysisResult",
 "properties": {
 "queryTextSentiment": {
@@ -14929,7 +14929,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata": {
-"description": "Metadata for a ConversationProfile.SetSuggestionFeatureConfig operation.",
+"description": "Metadata for a ConversationProfiles.SetSuggestionFeatureConfig operation.",
 "id": "GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata",
 "properties": {
 "conversationProfile": {
@@ -16992,7 +16992,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2beta1FewShotExample": {
-"description": "Providing examples in the generator (i.e. building a few-shot generator) helps convey the desired format of the LLM response. NEXT_ID: 10",
+"description": "Providing examples in the generator (i.e. building a few-shot generator) helps convey the desired format of the LLM response.",
 "id": "GoogleCloudDialogflowV2beta1FewShotExample",
 "properties": {
 "conversationContext": {
@@ -17285,7 +17285,7 @@ true
 },
 "summarizationContext": {
 "$ref": "GoogleCloudDialogflowV2beta1SummarizationContext",
-"description": "Input of prebuilt Summarization feature."
+"description": "Input of Summarization feature."
 },
 "triggerEvent": {
 "description": "Optional. The trigger event of the generator. It defines when the generator is triggered in a conversation.",
@@ -20485,7 +20485,7 @@ true
 "id": "GoogleCloudDialogflowV2beta1SearchKnowledgeRequestSearchConfigBoostSpecs",
 "properties": {
 "dataStores": {
-"description": "Optional. Data Stores where the boosting configuration is applied. The full names of the referenced data stores. Formats: `projects/{project}/locations/{location}/collections/{collection}/dataStores/{data_store}` `projects/{project}/locations/{location}/dataStores/{data_store}",
+"description": "Optional. Data Stores where the boosting configuration is applied. The full names of the referenced data stores. Formats: `projects/{project}/locations/{location}/collections/{collection}/dataStores/{data_store}` `projects/{project}/locations/{location}/dataStores/{data_store}`",
 "items": {
 "type": "string"
 },

googleapiclient/discovery_cache/documents/dialogflow.v3.json

@@ -4453,7 +4453,7 @@
 }
 }
 },
-"revision": "20241025",
+"revision": "20241119",
 "rootUrl": "https://dialogflow.googleapis.com/",
 "schemas": {
 "GoogleCloudDialogflowCxV3AdvancedSettings": {
@@ -4830,7 +4830,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3BargeInConfig": {
-"description": "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.",
+"description": "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.",
 "id": "GoogleCloudDialogflowCxV3BargeInConfig",
 "properties": {
 "noBargeInDuration": {
@@ -10371,7 +10371,7 @@ false
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3beta1BargeInConfig": {
-"description": "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.",
+"description": "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.",
 "id": "GoogleCloudDialogflowCxV3beta1BargeInConfig",
 "properties": {
 "noBargeInDuration": {
@@ -12721,7 +12721,7 @@ false
 "type": "object"
 },
 "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata": {
-"description": "Metadata for a ConversationProfile.ClearSuggestionFeatureConfig operation.",
+"description": "Metadata for a ConversationProfiles.ClearSuggestionFeatureConfig operation.",
 "id": "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata",
 "properties": {
 "conversationProfile": {
@@ -12913,7 +12913,7 @@ false
 "type": "object"
 },
 "GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata": {
-"description": "Metadata for ConversationDatasets.",
+"description": "Metadata for CreateConversationDataset.",
 "id": "GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata",
 "properties": {
 "conversationDataset": {
@@ -13002,7 +13002,7 @@ false
 "type": "object"
 },
 "GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata": {
-"description": "Metadata for ConversationDatasets.",
+"description": "Metadata for DeleteConversationDataset.",
 "id": "GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata",
 "properties": {},
 "type": "object"
@@ -14591,7 +14591,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SentimentAnalysisResult": {
-"description": "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",
+"description": "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",
 "id": "GoogleCloudDialogflowV2SentimentAnalysisResult",
 "properties": {
 "queryTextSentiment": {
@@ -14634,7 +14634,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata": {
-"description": "Metadata for a ConversationProfile.SetSuggestionFeatureConfig operation.",
+"description": "Metadata for a ConversationProfiles.SetSuggestionFeatureConfig operation.",
 "id": "GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata",
 "properties": {
 "conversationProfile": {

googleapiclient/discovery_cache/documents/dialogflow.v3beta1.json

@@ -5185,7 +5185,7 @@
 }
 }
 },
-"revision": "20241025",
+"revision": "20241119",
 "rootUrl": "https://dialogflow.googleapis.com/",
 "schemas": {
 "GoogleCloudDialogflowCxV3AdvancedSettings": {
@@ -5305,7 +5305,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3BargeInConfig": {
-"description": "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.",
+"description": "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.",
 "id": "GoogleCloudDialogflowCxV3BargeInConfig",
 "properties": {
 "noBargeInDuration": {
@@ -7915,7 +7915,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3beta1BargeInConfig": {
-"description": "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.",
+"description": "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.",
 "id": "GoogleCloudDialogflowCxV3beta1BargeInConfig",
 "properties": {
 "noBargeInDuration": {
@@ -10014,7 +10014,7 @@
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3beta1FlowInvocation": {
-"description": "Stores metadata of the invocation of a CX flow. Next Id: 7",
+"description": "Stores metadata of the invocation of a CX flow.",
 "id": "GoogleCloudDialogflowCxV3beta1FlowInvocation",
 "properties": {
 "flow": {
@@ -12077,7 +12077,7 @@ false
 "type": "object"
 },
 "GoogleCloudDialogflowCxV3beta1PlaybookInvocation": {
-"description": "Stores metadata of the invocation of a child playbook. Next Id: 5",
+"description": "Stores metadata of the invocation of a child playbook.",
 "id": "GoogleCloudDialogflowCxV3beta1PlaybookInvocation",
 "properties": {
 "playbook": {
@@ -12238,7 +12238,7 @@ false
 "type": "string"
 },
 "currentPlaybook": {
-"description": "Optional. Start the session with the specified playbook. You can only specify the playbook at the beginning of the session. Otherwise, an error will be thrown. Format: `projects//locations//agents//playbooks/`.",
+"description": "Optional. The unique identifier of the playbook to start or continue the session with. If `current_playbook` is specified, the previous state of the session will be ignored by Dialogflow. Format: `projects//locations//agents//playbooks/`.",
 "type": "string"
 },
 "disableWebhook": {
@@ -14791,7 +14791,7 @@ false
 "type": "object"
 },
 "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata": {
-"description": "Metadata for a ConversationProfile.ClearSuggestionFeatureConfig operation.",
+"description": "Metadata for a ConversationProfiles.ClearSuggestionFeatureConfig operation.",
 "id": "GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata",
 "properties": {
 "conversationProfile": {
@@ -14983,7 +14983,7 @@ false
 "type": "object"
 },
 "GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata": {
-"description": "Metadata for ConversationDatasets.",
+"description": "Metadata for CreateConversationDataset.",
 "id": "GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata",
 "properties": {
 "conversationDataset": {
@@ -15072,7 +15072,7 @@ false
 "type": "object"
 },
 "GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata": {
-"description": "Metadata for ConversationDatasets.",
+"description": "Metadata for DeleteConversationDataset.",
 "id": "GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata",
 "properties": {},
 "type": "object"
@@ -16661,7 +16661,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SentimentAnalysisResult": {
-"description": "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",
+"description": "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",
 "id": "GoogleCloudDialogflowV2SentimentAnalysisResult",
 "properties": {
 "queryTextSentiment": {
@@ -16704,7 +16704,7 @@ true
 "type": "object"
 },
 "GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata": {
-"description": "Metadata for a ConversationProfile.SetSuggestionFeatureConfig operation.",
+"description": "Metadata for a ConversationProfiles.SetSuggestionFeatureConfig operation.",
 "id": "GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata",
 "properties": {
 "conversationProfile": {