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. Custom Properties for Analyzing Deployments

Custom Property

Description

_debug_deployment

By default, all resources that are created by a provisioning process are rolled back if provisioning fails. 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. None of the components in the failed catalog item are accessible to the user, so this custom property is best used during development and testing of new application blueprints.

To apply the custom property to an application blueprint, add _debug_deployment to the Blueprint Properties page using the Properties tab when you create or edit an application blueprint.

This property is for blueprints that contain multiple components, such as composite blueprints, and is ignored if applied to standalone blueprints.

_deploymentName

Displays or hides the deployment name field from a published, composite blueprint in the provisioning request details form. To apply the custom property and display the name of the deployment in the request details form, add _deploymentName=true to the Blueprint Properties page using the Properties tab when you create or edit a blueprint. By default, the property is set to false, which suppresses the deployment name.