While maintaining deployments and networks, you might need the ability to relocate machines that you deployed with Automation Assembler.
For example, you might deploy to a test network first, then move to a production network. The technique described here lets you design a cloud template in advance to prepare for such day 2 actions. Note that the machine is moved. It isn't deleted and redeployed.
This procedure only applies to Cloud.vSphere.Machine resources. It won't work for cloud agnostic machines deployed to vSphere.
Prerequisites
- The Automation Assembler network profile must include all subnets that the machine will connect to. In Automation Assembler, you can check networks by going to .
The network profile must be in an account and region that are part of the appropriate Automation Assembler project for your users.
- Tag the two subnets with different tags. The example that follows assumes that test and prod are the tag names.
- The deployed machine must keep the same IP assignment type. It can't change from static to DHCP, or vice versa, while moving to another network.