aws lexv2-models update-intent
Updates the settings for an intent
Options
Name | Description |
---|---|
--intent-id <string> | The unique identifier of the intent to update |
--intent-name <string> | The new name for the intent |
--description <string> | The new description of the intent |
--parent-intent-signature <string> | The signature of the new built-in intent to use as the parent of this intent |
--sample-utterances <list> | New utterances used to invoke the intent |
--dialog-code-hook <structure> | The new Lambda function to use between each turn of the conversation with the bot |
--fulfillment-code-hook <structure> | The new Lambda function to call when all of the intents required slots are provided and the intent is ready for fulfillment |
--slot-priorities <list> | A new list of slots and their priorities that are contained by the intent |
--intent-confirmation-setting <structure> | New prompts that Amazon Lex sends to the user to confirm the completion of an intent |
--intent-closing-setting <structure> | The new response that Amazon Lex sends the user when the intent is closed |
--input-contexts <list> | A new list of contexts that must be active in order for Amazon Lex to consider the intent |
--output-contexts <list> | A new list of contexts that Amazon Lex activates when the intent is fulfilled |
--kendra-configuration <structure> | New configuration settings for connecting to an Amazon Kendra index |
--bot-id <string> | The identifier of the bot that contains the intent |
--bot-version <string> | The version of the bot that contains the intent. Must be DRAFT |
--locale-id <string> | The identifier of the language and locale where this intent is used. The string must match one of the supported locales. For more information, see https://docs.aws.amazon.com/lex/latest/dg/supported-locales.html |
--cli-input-json <string> | Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally |
--generate-cli-skeleton <string> | Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command |