Customization specifications let you apply guest operating system settings at deployment time, when deploying to vSphere based cloud zones.
The customization specification must exist in vSphere, at the target that you deploy to.
Edit the blueprint code directly. The following example points to a
cloud-assembly-linux customization specification for a WordPress host on vSphere.
resources: WebTier: type: Cloud.vSphere.Machine properties: name: wordpress cpuCount: 2 totalMemoryMB: 1024 imageRef: 'Template: ubuntu-18.04' customizationSpec: 'cloud-assembly-linux' resourceGroupName: '/Datacenters/Datacenter/vm/deployments'
Customization specifications versus initialization commands
If you want the provisioning experience to match what you are currently doing in vSphere, continuing to use customization specifications might be the best approach. However, to expand to hybrid or multiple cloud provisioning, a more neutral approach is to embed initialization commands in a cloudConfig section of a blueprint.
For more about cloudConfig sections in blueprints, see Configuration commands in vRealize Automation Cloud Assembly blueprints.