7.4

Custom Properties for Naming and Analyzing Deployments
If provisioning fails, vRealize Automation rolls back all resources included in the catalog item. For
deployments that contain multiple components, you can use a custom property to override that default
and receive information to debug the failure. These properties are best used when applied to the overall
blueprint.
Table 1‑2. Custom Properties for Analyzing Deployments
Custom Property Description
_debug_deployment
Except for scale operations which allow partially successful
deployments, the default behavior is to destroy the entire
deployment if any of the individual resources fail to provision.
You can override the default behavior by setting the
_debug_deployment custom property value to true. If
provisioning fails, the debugging custom property stops the
resources from being rolled back so you can identify which of
the components failed to provision successfully.
A failed catalog item is inaccessible because it is immediately
rolled back on failure. But when _debug_deployment is set to
true, vRealize Automation treats the otherwise failed deployment
as partially successful, which enables its accessibility. This
behavior matches how failures are treated in scale operations.
If a virtual machine deployment fails, the deployment process
does not have awareness of the machine being provisioned. If it
is not provisioned, then there is nothing for the
_debug_deployment preserve from being rolled back.
To apply the custom property to a blueprint, add
_debug_deployment to the Blueprint Properties page using
the Properties tab when you create or edit a blueprint. The
_debug_deployment property is consumed at the software
provisioning level, not the guest agent or machine provisioning
level.
You can also configure vRealize Automation to not delete virtual
machines after deployment failure by using settings in the
VRMAgent.exe.config file.
_deploymentName
When added to a blueprint, this property allows you to specify a
custom name for the deployment by setting the value of
_deploymentName to your custom string. If more than one
instance of this deployment is provisioned in a single request,
your custom name becomes a prefix. If you want users to
specify their own deployment names, set this custom property to
allow override. The following two caveats are required for usage:
n
You must add this property at the blueprint level, not at the
component level. For example, when creating or editing a
blueprint, click the Properties tab and then select Custom
Properties > New to add the _deploymentName property to
the blueprint. Do not add the property to a machine or other
component in the blueprint.
n
You must add this property as a separate property and not
as a member of a property group.
Custom Properties Reference
VMware, Inc. 14