- Newest
- Most votes
- Most comments
Hello!
Thank you for reaching out regarding the Lex Cloud Formation feature.
The AWS::Lex::BotVersion resource was designed to be treated as an immutable resource. Think of it as a solution if you want to codify a working version that will be saved for the future. An example would be a production version (with corresponding alias) and a pre-production version. Thus this resource is not as useful if there is a need to test or develop while wanting to publish a new version every iteration.
However there is a mechanism you can use to accomplish creating a new version with every CFN iteration. You can modify the CloudFormation primary identifier for the AWS::Lex::BotVersion resource when you want to update your BotVersion. For your example it would be changing the PrimaryID ReschedulingBotVersion to ReschedulingBotVersionTwo. This will effectively delete corresponding BotVersion #1 and create a new BotVersion #2. In the event you want to keep existing bot versions, you would need to create a separate BotVersion resource to avoid deletion.
If there's any more questions please feel free to comment again and we'll try to address any issues.
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 7 months ago