Aria Automation policy
Create, update, and delete Aria Automation policies in OneFuse
3 minute read
Setup overview
- Create an Aria Automation Module Credential.
- Create a VMware Aria Automation Endpoint. If applicable, configure VMware Aria Automation proxy support.
- Create a VMware Aria Automation Policy.
- Execute the Aria Automation Policy to create managed vRA Deployments.
The user setting up the Aria Automation Policy must have the credentials to log in to the Aria Automation instance.
Create an Aria Automation Policy
Prerequisite
Create a Module Credential and Endpoint for the selected technology.
- In OneFuse, select Aria Automation from Home, or select Modules > Aria Automation from the left navigation menu.
- Select Create and fill out the Aria Automation Policy form.
- Select Next.
Edit an Aria Automation Policy
- In OneFuse, select Aria Automation under Modules, or select Modules > Aria Automation from the left navigation menu.
- Locate the policy to edit and select the edit icon.
- Go to the correct tab using the Next and Back buttons at the top of the page.
- Select Update to save the changes.
Delete an Aria Automation Policy
An Aria Automation Policy cannot be deleted if it is associated with an existing Aria Automation Deployment managed object. Remove or unregister any deployments attached to this policy before deleting.
- In OneFuse, select Aria Automation under Modules, or select Modules > Aria Automation from the left navigation menu.
- Locate the policy under Aria Automation Policies, or search for it, and select the delete icon.
Aria Automation Policy form fields
| Field | Description |
|---|---|
| Aria Automation Policy Name | Enter a name for this policy. |
| Description | Optional description for this Aria Automation policy. |
| Endpoint Type | Select the Endpoint Type for this Aria Automation Policy. |
| Endpoint Name | Select the Endpoint Name for this policy. |
| Cloud Template Name | Enter the Aria Automation Cloud Template name. |
| Cloud Template Version Number | Enter the Aria Automation Cloud Template version number. |
| Cloud Template Inputs | Optional. Enter Cloud Template Inputs using a mix of static and templated text in JSON format. Enter any combination of inputs that the vRA Cloud Template is configured to accept. For example, {"cpuCount": 1, "totalMemoryMB": 1024} passes cpuCount and totalMemoryMB to the Cloud Template. If left blank, OneFuse will not pass any inputs to Aria Automation and the defaults on the Cloud Template will be used. |
| Blueprint ID | Optional. Enter the Aria Automation Blueprint ID. |
| Project Name | Optional. Enter the Aria Automation project name. |
| User Mapping | Optional. Enter the Deployment Owner using a mix of static and templated text. If using templating, the specified properties must be passed in via template_properties. |
Next steps
Now that you have created an Aria Automation Policy, Provision with VMware Aria Automation.