This tutorial will walk you through how to use the “Migrating from launches to stacks” feature.
We will assume you have:
We will assume you are comfortable:
Here are the steps you need to follow to “Migrating from launches to stacks”
Your manifest should contain a launch:
launches:
basic-vpc:
portfolio: ccoe
product: basic-vpc
version: v1
deploy_to:
tags:
- tag: group:spoke
regions: regions_enabled
You will need to remove the launch named basic-vpc from your manifest file and add a stack to your manifest file. You can name the stack whatever you want. You will need to add an attribute named launch_name with the value of basic-vpc where basic-vpc is the launch name you used previously. In this example it looks like this:
stacks:
basic-vpc:
name: basic-vpc
version: v1
launch_name: basic-vpc
deploy_to:
tags:
- tag: group:spoke
regions: regions_enabled
When you make this change the framework will look for a provisioned product in the spoke account named basic-vpc. If it finds it, it will use your new (stack) template to update the CloudFormation stack your previous launch created. You should not terminate the provisioned product unless you want to terminate the resources. If you terminate the product or if the product does not exist in the spoke account a new stack will be created using the stack name from the manifest file as the CloudFormation stack name.
With this approach you can migrate a launch to a stack. In existing accounts the stack from the provisioned product will be used (with a name of SC-<account_id>-<pp_id>) and in accounts where the stack from the product was never provisioned a new stack will be created using the manifest file stack name.