7.3
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Custom Properties and the Property Dictionary
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Deployments
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for OpenStack Endpoints
- Custom Properties for Clone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Linux Kickstart Blueprints
- Custom Properties for SCCM Blueprints
- Custom Properties for WIM Blueprints
- Custom Properties for vCloud Air and vCloud Director Blueprints
- Custom Properties for Networking
- Custom Properties and Property Groups for Containers
- Custom Properties for PXE Provisioning
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties Underscore (_)
- Custom Properties A
- Custom Properties B
- Custom Properties C
- Custom Properties E
- Custom Properties H
- Custom Properties I
- Custom Properties L
- Custom Properties M
- Custom Properties N
- Custom Properties O
- Custom Properties P
- Custom Properties R
- Custom Properties S
- Custom Properties V
- Custom Properties X
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Defining Component Profile Settings
Custom Properties Grouped by Name
You can use custom properties to provide additional vRealize Automation controls.
Custom properties have been grouped here by name. To explore custom properties grouped by function,
see Custom Properties Grouped by Function.
Custom Properties Underscore (_)
A list of vRealize Automation custom properties that begin with an underscore (_).
Table 1‑30. Custom Properties Underscore (_) Table
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. 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.
_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.
Custom Properties Reference
VMware, Inc. 59