Appendix A. Inventory file variables
The following tables contain information about the pre-defined variables used in Ansible installation inventory files.
Not all of these variables are required.
A.1. General variables
Variable | Description |
---|---|
|
The default install registers the node to the Red Hat Insights for Red Hat Ansible Automation Platform Service if the node is registered with Subscription Manager. Set to
Default = |
|
Password credential for access to
Used for both
Enter your Red Hat Registry Service Account credentials in
When |
|
Used for both
Default = |
|
User credential for access to
Used for both
Enter your Red Hat Registry Service Account credentials in |
A.2. Ansible automation hub variables
Variable | Description |
---|---|
| Required |
| If upgrading from Ansible Automation Platform 2.0 or earlier, you must either:
Generating a new token invalidates the existing token. |
|
This variable is not set by default. Set it to
When this is set to
|
| If a collection signing service is enabled, collections are not signed automatically by default.
Setting this parameter to
Default = |
| Optional
Ansible automation hub provides artifacts in
You can also set
Default = |
| If a collection signing service is enabled, you must provide this variable to ensure collections can be properly signed.
|
| If a collection signing service is enabled, you must provide this variable to ensure collections can be properly signed.
|
|
The default install does not create a signing service. If set to
Default = |
| The default install deploys a TLS enabled Ansible automation hub. Use if automation hub is deployed with HTTP Strict Transport Security (HSTS) web-security policy enabled. Unless specified otherwise, the HSTS web-security policy mechanism is enabled. This setting allows you to disable it if required.
Default = |
| Optional If Ansible automation hub is deployed with HTTPS enabled.
Default = |
|
When set to
Default = |
| Optional Dictionary of setting to pass to galaxy-importer. At import time collections can go through a series of checks.
Behavior is driven by
Examples are This parameter enables you to drive this configuration. |
For Ansible automation hub to connect to LDAP directly; the following variables must be configured. A list of other LDAP related variables (not covered by the automationhub_ldap_xxx
variables below) that can be passed using the ldap_extra_settings
variable can be found here: https://django-auth-ldap.readthedocs.io/en/latest/reference.html#settings
Variable | Description |
---|---|
|
The name to use when binding to the LDAP server with |
| Required
The password to use with |
|
An LDAPSearch object that finds all LDAP groups that users might belong to. If your configuration makes any references to LDAP groups, this and
Default = |
| Optional Search filter for finding group membership.
Default = |
| Optional
Default = |
| Optional
Default = |
| The URI of the LDAP server. This can be any URI that is supported by your underlying LDAP libraries. |
| An LDAPSearch object that locates a user in the directory. The filter parameter should contain the placeholder %(user)s for the username. It must return exactly one result for authentication to succeed. |
|
When using Single Sign-On, specify the main automation hub URL that clients will connect to, for example,
If not specified, the first node in the |
| Required The database name.
Default = |
| Required if not using internal database. |
| The password for the automation hub PostgreSQL database.
Do not use special characters for |
| Required if not using internal database. Default = 5432 |
| Required.
Default = |
| Required
Default = |
| Optional If automation hub enforces the approval mechanism before collections are made available. By default when you upload collections to automation hub an administrator must approve it before it is made available to the users.
If you want to disable the content approval flow, set the variable to
Default = |
| Optional
|
| Optional
Same as |
| For Red Hat Ansible Automation Platform 2.2 and later, this value is no longer used. If automation hub should validate certificate when requesting itself because by default, Ansible Automation Platform deploys with self-signed certificates.
Default = |
| If upgrading from Red Hat Ansible Automation Platform 2.0 or earlier, you must either:
|
| Relative or absolute path to the Fernet symmetric encryption key you want to import. The path is on the Ansible management node. It is used to encrypt certain fields in the database (such as credentials.) If not specified, a new key will be generated. |
A.3. Red Hat Single Sign-On variables
*Use these variables for automationhub
or automationcatalog
.
Variable | Description |
---|---|
| Optional Used for Ansible Automation Platform managed and externally managed Red Hat Single Sign-On. Path to the directory where theme files are located. If changing this variable, you must provide your own theme files.
Default = |
| Optional Used for Ansible Automation Platform managed and externally managed Red Hat Single Sign-On. The name of the realm in SSO.
Default = |
| Optional Used for Ansible Automation Platform managed and externally managed Red Hat Single Sign-On. Display name for the realm.
Default = |
| Optional Used for Ansible Automation Platform managed and externally managed Red Hat Single Sign-On. SSO administration username.
Default = |
| Required Used for Ansible Automation Platform managed and externally managed Red Hat Single Sign-On. SSO administration password. |
| Optional Used for Ansible Automation Platform managed Red Hat Single Sign-On only. Customer-provided keystore for SSO. |
| Required Used for Ansible Automation Platform externally managed Red Hat Single Sign-On only. Automation hub and Automation services catalog require SSO and SSO administration credentials for authentication. SSO administration credentials are also required to set automation services catalog specific roles needed for the application. If SSO is not provided in the inventory for configuration, then you must use this variable to define the SSO host. |
| Optional Used for Ansible Automation Platform managed Red Hat Single Sign-On only.
Set to
Default = |
| Optional Used for Ansible Automation Platform managed Red Hat Single Sign-On only. Name of keystore for SSO.
Default = |
| Password for keystore for HTTPS enabled SSO.
Required when using Ansible Automation Platform managed SSO and when HTTPS is enabled. The default install deploys SSO with |
| Optional Used for Ansible Automation Platform managed and externally managed Red Hat Single Sign-On.
If This must be reachable from client machines. |
| Optional Used for Ansible Automation Platform managed and externally managed Red Hat Single Sign-On.
Set to
Default = |
| Optional Used for Ansible Automation Platform managed and externally managed Red Hat Single Sign-On. If Single Sign On uses https.
Default = |
A.4. Automation services catalog variables
Variable | Description |
---|---|
| Used to generate a token from a controller host.
Requires |
| Used for a pre-created OAuth token for automation controller. This token will be used instead of generating a token. |
|
Used to generate a token from a controller host. Requires |
| Used to enable or disable SSL validation from automation services catalog to automation controller.
Default = |
| Used to enable or disable HSTS web-security policy for automation services catalog. Default = `false. |
| Used to enable or disable HSTS web-security policy for Services Catalog.
Default = |
| Used to control activation of analytics collection for automation services catalog |
| Used by the Red Hat Single Sign-On host configuration if there is an alternative hostname that needs to be used between the SSO and automation services catalog host. |
| The postgres database URL for your automation services catalog. |
| The PostgreSQL host (database node) for your automation services catalog |
| The password for the PostgreSQL database of your automation services catalog.
Do not use special characters for |
| The PostgreSQL port to use for your automation services catalog. Default = 5432 |
| The postgres ID for your automation services catalog. |
|
Path to a custom provided SSL certificate file. Requires |
| Path to a custom provided SSL certificate key file.
Requires The internally managed CA signs and creates the certificate if not provided and https is left enabled. |
A.5. Automation controller variables
Variable | Description |
---|---|
| The password for an administration user to access the UI upon install completion. |
| For an alternative front end URL needed for SSO configuration with automation services catalog, provide the URL. Automation services catalog requires either Controller to be installed with automation controller, or a URL to an active and routable Controller server must be provided with this variable |
| Password for your automation controller instance. |
| Username for your automation controller instance. |
| Optional
The status of a node or group of nodes. Valid options are
Default = |
|
For
Two valid
A
A
Default for this group =
For Two valid node_types can be assigned for this group.
A
A
Default for this group = |
| Optional Peer relationships define node-to-node connections.
This variable is used to add
The peers variable can be a comma-separated list of hosts and/or groups from the inventory. This is resolved into a set of hosts that is used to construct the |
| The name of the postgres database.
Default = |
| The postgreSQL host, which can be an externally managed database. |
| The password for the postgreSQL database.
Do not use special characters for NOTE
You no longer need to provide a
When you supply |
| The postgreSQL port to use. Default = 5432 |
|
One of
Set to
Default = |
| Your postgres database username.
Default = |
| location of postgres ssl certificate.
|
`postgres_ssl_key | location of postgres ssl key.
|
| Location of postgres user certificate.
|
| Location of postgres user key.
|
| If postgres is to use SSL. |
| Port to use for recptor connection. Default = 27199. |
| Optional
Same as |
| Optional
Same as |
A.6. Ansible variables
The following variables control how Ansible Automation Platform interacts with remote hosts.
Additional information on variables specific to certain plugins can be found at https://docs.ansible.com/ansible-core/devel/collections/ansible/builtin/index.html
A list of global configuration options can be found at https://docs.ansible.com/ansible-core/devel/reference_appendices/config.html
Variable | Description |
---|---|
| The connection plugin used for the task on the target host.
This can be the name of any of ansible connection plugin. SSH protocol types are
Default = |
|
The ip or name of the target host to use instead of |
| The connection port number, if not, the default (22 for ssh). |
| The user name to use when connecting to the host. |
| The password to use to authenticate to the host. Never store this variable in plain text. Always use a vault. |
| Private key file used by ssh. Useful if using multiple keys and you do not want to use an SSH agent. |
|
This setting is always appended to the default command line for |
|
This setting is always appended to the default |
|
This setting is always appended to the default |
|
This setting is always appended to the default |
|
Determines if SSH pipelining is used. This can override the pipelining setting in |
| |
| This variable sets the SSH user for the installer to use and defaults to root. This user must allow SSH-based authentication without requiring a password. If using SSH key-based authentication, then the key must be managed by an SSH agent. |
| (added in version 2.2)
This setting overrides the default behavior to use the system ssh. This can override the ssh_executable setting in |
|
The shell type of the target system. You should not use this setting unless you have set the |
|
This sets the shell that the ansible controller uses on the target machine, and overrides the executable in
You should only change if it is not possible to use |
The following variables cannot be set directly by the user. Ansible will always override them to reflect internal state.
Variable | Description |
---|---|
| Boolean that indicates if we are in check mode or not |
| The names of the roles currently imported into the current play as dependencies of other plays |
|
Contents of the |
|
A dictionary or map containing extended loop information when enabled using |
| The name of the value provided to loop_control.loop_var. Added in 2.8 |
|
The name of the value provided to |
|
When the current role is being executed by means of an
For example: When role A includes role B, inside role B, |
|
When the current role is being executed by means of an |
|
List of active hosts in the current play run limited by the serial, aka |
| List of hosts in the current play run, not limited by the serial. Failed or unreachable hosts are excluded from this list. |
| List of all the hosts that were targeted by the play |
| The names of the roles currently imported into the current play. This list does not contain the role names that are implicitly included through dependencies. |
| The name of the currently executed play. Added in 2.8. (name attribute of the play, not file name of the playbook.) |
| Current search path for action plugins and lookups, in other words, where we search for relative paths when you do template: src=myfile |
|
Dictionary or map that contains information about the current running version of ansible, it has the following keys: |