class Aws::LexModelBuildingService::Types::StartMigrationRequest
@note When making an API call, you may pass StartMigrationRequest
data as a hash: { v1_bot_name: "BotName", # required v1_bot_version: "Version", # required v2_bot_name: "V2BotName", # required v2_bot_role: "IamRoleArn", # required migration_strategy: "CREATE_NEW", # required, accepts CREATE_NEW, UPDATE_EXISTING }
@!attribute [rw] v1_bot_name
The name of the Amazon Lex V1 bot that you are migrating to Amazon Lex V2. @return [String]
@!attribute [rw] v1_bot_version
The version of the bot to migrate to Amazon Lex V2. You can migrate the `$LATEST` version as well as any numbered version. @return [String]
@!attribute [rw] v2_bot_name
The name of the Amazon Lex V2 bot that you are migrating the Amazon Lex V1 bot to. * If the Amazon Lex V2 bot doesn't exist, you must use the `CREATE_NEW` migration strategy. * If the Amazon Lex V2 bot exists, you must use the `UPDATE_EXISTING` migration strategy to change the contents of the Amazon Lex V2 bot. @return [String]
@!attribute [rw] v2_bot_role
The IAM role that Amazon Lex uses to run the Amazon Lex V2 bot. @return [String]
@!attribute [rw] migration_strategy
The strategy used to conduct the migration. * `CREATE_NEW` - Creates a new Amazon Lex V2 bot and migrates the Amazon Lex V1 bot to the new bot. * `UPDATE_EXISTING` - Overwrites the existing Amazon Lex V2 bot metadata and the locale being migrated. It doesn't change any other locales in the Amazon Lex V2 bot. If the locale doesn't exist, a new locale is created in the Amazon Lex V2 bot. @return [String]
@see docs.aws.amazon.com/goto/WebAPI/lex-models-2017-04-19/StartMigrationRequest AWS API Documentation
Constants
- SENSITIVE