Custom Properties for Blueprints and Deployments

vRealize Automation provides a number of custom properties that are generally applicable to all or most blueprints and deployments. You can set many of these properties in the vRealize Automation user interface without using custom properties.

Table 1. Custom Properties for Blueprints and 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. None of the components in a failed catalog item are accessible to users, so this custom property is best used during development and testing of new blueprints. 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. This property is for blueprints that contain multiple components, such as composite blueprints, and is ignored if applied to standalone blueprints. The _debug_deployment property is consumed at the software provisioning level, not the guest agent or machine provisioning level.
_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: 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. You must add this property as a separate property and not as a member of a property group.
_number_of_instances	When added to a blueprint, this property allows you to specify the number of instances of the deployment that a user can provision in a single request.