Managing Your Deployment Using vRealize Automation Cloud Assembly APIs

This use case includes examples of procedures you can follow to reconfigure your deployment after initial blueprint deployment. The first example deploys a new blueprint with a deployment ID, and in subsequent examples, you use the deployment ID to update the deployment or reconfigure the blueprint components.

Prerequisites for Managing Your Deployment

All tasks for managing your deployment share the following common prerequisites:

• Verify that you are at least an organization member in VMware vRealize Automation with a vRealize Automation Cloud Assembly administrator service role.
• Verify that you have an active access token. See Getting Your Authentication Token.
• Verify that the URL variable is assigned.

  url='https://appliance.domain.com'

• Verify that the API version variable is assigned to a date as in the following example.

  api_version='2019-09-12'

  It is not necessary to lock your use case to the date provided in the example. To integrate your use case with the API and lock it to a particular date, you can enter any date you choose. Or if you choose to consume the API without versioning, leave the apiVersion value unspecified and the latest API version is used by default. Backward compatibility is not preserved, but your use case automatically benefits from improvements or enhancements to the API.

• Verify that you have the ID for a project that is associated with the deployment that you are managing. See Request Deployment.
• Verify that the flavor mapping and image mapping specified in the blueprint to be deployed exist in your cloud account. See Create Flavor Mappings and Create Image Mappings.
• Verify that the cloud zone that you are deploying into is associated with your project. See Add a Cloud Zone to Your Project.
• Verify that a network profile is configured for the cloud account associated with the project. See Create Network Profiles.

Any additional prerequisites are specified with the individual tasks.