7.1
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Blueprints and 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 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 (_) Table
- Custom Properties A Table
- Custom Properties B Table
- Custom Properties C Table
- Custom Properties E Table
- Custom Properties H Table
- Custom Properties I Table
- Custom Properties L Table
- Custom Properties M Table
- Custom Properties O Table
- Custom Properties P Table
- Custom Properties R Table
- Custom Properties S Table
- Custom Properties V Table
- Custom Properties X Table
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Index
Custom Properties Underscore (_) Table
This section lists vRealize Automation custom properties that begin with an underscore (_).
Table 3‑1. 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 seing 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.
You can also congure vRealize Automation to not delete
virtual machines after deployment failure by using seings in
the VRMAgent.exe.config le.
_deploymentName
When added to a blueprint, this property allows you to specify
a custom name for the deployment by seing 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 prex. 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
50 VMware, Inc.