Red Hat Ansible Tower - Run Command

Article summary

Did you find this summary helpful?

Thank you for your feedback

Red Hat Ansible Tower - Run Command runs a Red Hat Ansible command on:

Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

Note:

Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.

General Settings

Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

Use stored credentials from the Red Hat Automation Controller (Ansible Tower) adapter - Select this option to use the the first connected Red Hat Automation Controller (Ansible Tower) adapter credentials.
Note:
To use this option, you must successfully configure a Red Hat Automation Controller (Ansible Tower) adapter connection.

These fields must be configured to run the Enforcement Set.

Ansible Tower Domain - The domain of the Red Hat Ansible Tower on which to run the command. This field is filled in automatically when Use stored credentials... is enabled
Name - The name of the command.
Organization ID - The ID of the organization within Red Hat Ansible Tower.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

These fields are optional.

User Name and Password - The credentials for a user account that has the Required Permissions to perform this Enforcement Action.
API Token - The API token for the supplied username and password.
Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

Description - Description of the command.
Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.
Note:
For details, see Axonius to External Field Mapping.
Additional fields - Specify additional fields to be added as key/value pairs in a JSON format.
For example:
```
{"field1": "value1", "field2": "value2"}
```
If one of the specified fields is invalid, the request might fail.
Gateway Name - Select the Gateway through which to connect to perform the action.

The values supplied in Connection Parameters above must have the permissions to perform the command you want to run.

For more details about other Enforcement Actions available, see Action Library.

Was this article helpful?

Table of contents