此内容没有您所选择的语言版本。
Appendix A. Inventory file variables
The following tables contain information about the variables used in Ansible Automation Platform’s installation inventory
files. The tables include the variables that you can use for RPM-based installation and container-based installation.
A.1. Ansible variables
The following variables control how Ansible Automation Platform interacts with remote hosts.
For more information about variables specific to certain plugins, see the documentation for Ansible.Builtin.
For a list of global configuration options, see Ansible Configuration Settings.
Variable | Description |
---|---|
| The connection plugin used for the task on the target host.
This can be the name of any of Ansible connection plugins. SSH protocol types are
Default = |
|
The IP address or name of the target host to use instead of |
| The password to authenticate to the host. Do not store this variable in plain text. Always use a vault. For more information, see Keep vaulted variables safely visible. |
| The connection port number.
The default for SSH is |
|
This setting is always appended to the default |
|
This setting is always appended to the default |
|
This sets the shell that the Ansible controller uses on the target machine and overrides the executable in |
| The shell type of the target system.
Do not use this setting unless you have set the |
|
This setting is always appended to the default command line for |
|
This setting overrides the default behavior to use the system |
|
This setting is always appended to the default |
|
Determines if SSH
This can override the |
| Private key file used by SSH. Useful if using multiple keys and you do not want to use an SSH agent. |
| The user name to use when connecting to the host.
Do not change this variable unless |
| This variable takes the hostname of the machine from the inventory script or the Ansible configuration file. You cannot set the value of this variable. Because the value is taken from the configuration file, the actual runtime hostname value can vary from what is returned by this variable. |
A.2. Automation hub variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
|
|
Automation hub administrator password. | Required | |
|
Set the existing token for the installation program. | Optional | ||
|
|
If a collection signing service is enabled, collections are not signed automatically by default. | Optional |
|
|
Ansible automation hub provides artifacts in | Optional |
| |
|
| Maximum allowed size for data sent to automation hub through NGINX. | Optional |
|
| Denote whether or not the collection download count should be displayed in the UI. | Optional |
| |
|
Controls the type of content to upload when | Optional | Both certified and validated are enabled by default. | |
|
| Path to the collection signing key file. | Required if a collection signing service is enabled. | |
|
Denote whether or not to run the command | Optional |
| |
|
| Path to the container signing key file. | Required if a container signing service is enabled. | |
|
|
Set this variable to | Optional |
|
|
|
Set this variable to | Optional |
|
|
|
Controls whether HTTP Strict Transport Security (HSTS) is enabled or disabled for automation hub. | Optional |
|
|
|
Controls whether HTTPS is enabled or disabled for automation hub. | Optional |
|
|
Controls whether logging is enabled or disabled at | Optional |
| |
|
Controls whether read-only access is enabled or disabled for unauthorized users viewing collections or namespaces for automation hub. | Optional |
| |
|
Controls whether or not unauthorized users can download read-only collections from automation hub. | Optional |
| |
|
| The firewall zone where automation hub related firewall rules are applied. This controls which networks can access automation hub based on the zone’s trust level. | Optional |
RPM = no default set. Container = |
|
Denote whether or not to require the change of the default administrator password for automation hub during installation. | Optional |
| |
|
|
Dictionary of settings to pass to the | Optional | |
|
Denote whether the web certificate sources are local to the installation program ( | Optional |
The value defined in | |
|
|
Controls whether client certificate authentication is enabled or disabled on the automation hub PostgreSQL database. | Optional |
|
|
| Name of the PostgreSQL database used by automation hub. | Optional |
RPM = |
|
| Hostname of the PostgreSQL database used by automation hub. | Required |
RPM = |
|
|
Password for the automation hub PostgreSQL database user. | Optional | |
|
| Port number for the PostgreSQL database used by automation hub. | Optional |
|
|
|
Controls the SSL/TLS mode to use when automation hub connects to the PostgreSQL database. | Optional |
|
|
| Username for the automation hub PostgreSQL database user. | Optional |
RPM = |
|
| Path to the PostgreSQL SSL/TLS certificate file for automation hub. | Required if using client certificate authentication. | |
|
| Path to the PostgreSQL SSL/TLS key file for automation hub. | Required if using client certificate authentication. | |
|
Denote whether the PostgreSQL client certificate sources are local to the installation program ( | Optional |
The value defined in | |
|
Controls whether content signing is enabled or disabled for automation hub. | Optional |
| |
|
Controls whether or not existing signing keys should be restored from a backup. | Optional |
| |
|
|
Controls whether or not pre-loading of collections is enabled. | Optional |
|
|
| Path to the SSL/TLS certificate file for automation hub. | Optional | |
|
| Path to the SSL/TLS key file for automation hub. | Optional | |
|
|
Denote whether the automation hub provided certificate files are local to the installation program ( | Optional |
|
|
| List of additional NGINX headers to add to automation hub’s NGINX configuration. | Optional |
|
|
Controls whether or not a token is generated for automation hub during installation. By default, a token is automatically generated during a fresh installation. | Optional |
| |
| Defines additional settings for use by automation hub during installation. For example: hub_extra_settings: - setting: REDIRECT_IS_HTTPS value: True | Optional |
| |
|
| Maximum duration (in seconds) that HTTP Strict Transport Security (HSTS) is enforced for automation hub. | Optional |
|
|
| Secret key value used by automation hub to sign and encrypt data. | Optional | |
| Azure blob storage account key. | Required if using an Azure blob storage backend. | ||
| Account name associated with the Azure blob storage. | Required when using an Azure blob storage backend. | ||
| Name of the Azure blob storage container. | Optional |
| |
|
Defines extra parameters for the Azure blob storage backend. | Optional |
| |
| Password for the automation content collection signing service. | Required if the collection signing service is protected by a passphrase. | ||
| Service for signing collections. | Optional |
| |
| Password for the automation content container signing service. | Required if the container signing service is protected by a passphrase. | ||
| Service for signing containers. | Optional |
| |
| Port number that automation hub listens on for HTTP requests. | Optional |
| |
| Port number that automation hub listens on for HTTPS requests. | Optional |
| |
|
| Protocols that automation hub will support when handling HTTPS traffic. | Optional |
RPM = |
| UNIX socket used by automation hub to connect to the PostgreSQL database. | Optional | ||
| AWS S3 access key. | Required if using an AWS S3 storage backend. | ||
| Name of the AWS S3 storage bucket. | Optional |
| |
|
Used to define extra parameters for the AWS S3 storage backend. | Optional |
| |
| AWS S3 secret key. | Required if using an AWS S3 storage backend. | ||
| Mount options for the Network File System (NFS) share. | Optional |
| |
| Path to the Network File System (NFS) share with read, write, and execute (RWX) access. |
Required if installing more than one instance of automation hub with a | ||
|
Automation hub storage backend type. | Optional |
| |
| Number of automation hub workers. | Optional |
|
A.3. Automation controller variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
|
| Email address used by Django for the admin user for automation controller. | Optional |
|
|
|
Automation controller administrator password. | Required | |
|
| Username used to identify and create the administrator user in automation controller. | Optional |
|
|
| Maximum allowed size for data sent to automation controller through NGINX. | Optional |
|
|
|
Controls whether client certificate authentication is enabled or disabled on the automation controller PostgreSQL database. | Optional |
|
|
| The firewall zone where automation controller related firewall rules are applied. This controls which networks can access automation controller based on the zone’s trust level. | Optional |
|
|
Denote whether the web certificate sources are local to the installation program ( | Optional |
The value defined in | |
|
Denote whether the PostgreSQL client certificate sources are local to the installation program ( | Optional |
The value defined in | |
|
|
Denote whether the automation controller provided certificate files are local to the installation program ( | Optional |
|
|
|
Controls whether HTTP Strict Transport Security (HSTS) is enabled or disabled for automation controller. | Optional |
|
|
|
Controls whether HTTPS is enabled or disabled for automation controller. | Optional |
|
|
| Maximum duration (in seconds) that HTTP Strict Transport Security (HSTS) is enforced for automation controller. | Optional |
|
|
| Port number that automation controller listens on for HTTP requests. | Optional |
RPM = |
|
| Port number that automation controller listens on for HTTPS requests. | Optional |
RPM = |
|
| Protocols that automation controller supports when handling HTTPS traffic. | Optional |
RPM = |
|
| List of additional NGINX headers to add to automation controller’s NGINX configuration. | Optional |
|
|
The status of a node or group of nodes. | Optional |
| |
|
See |
For the
For the
| Optional |
For |
|
See |
Used to indicate which nodes a specific host or group connects to. Wherever this variable is defined, an outbound connection to the specific host or group is established. | Optional | |
|
| Name of the PostgreSQL database used by automation controller. | Optional |
|
|
| Hostname of the PostgreSQL database used by automation controller. | Required | |
|
|
Password for the automation controller PostgreSQL database user. | Required if not using client certificate authentication. | |
|
| Port number for the PostgreSQL database used by automation controller. | Optional |
|
|
|
Controls the SSL/TLS mode to use when automation controller connects to the PostgreSQL database. | Optional |
|
|
| Username for the automation controller PostgreSQL database user. | Optional |
|
|
| Path to the PostgreSQL SSL/TLS certificate file for automation controller. | Required if using client certificate authentication. | |
|
| Path to the PostgreSQL SSL/TLS key file for automation controller. | Required if using client certificate authentication. | |
|
Number of hours worth of events table partitions to pre-create before starting a backup to avoid | Optional | 3 | |
|
|
Number of requests | Optional |
|
|
| Path to the SSL/TLS certificate file for automation controller. | Optional | |
|
| Path to the SSL/TLS key file for automation controller. | Optional | |
| Number of event workers that handle job-related events inside automation controller. | Optional |
| |
| Defines additional settings for use by automation controller during installation. For example: controller_extra_settings: - setting: USE_X_FORWARDED_HOST value: true | Optional |
| |
|
Path to the automation controller license file. | |||
| Memory allocation for automation controller. | Optional |
| |
| UNIX socket used by automation controller to connect to the PostgreSQL database. | Optional | ||
| Secret key value used by automation controller to sign and encrypt data. | Optional |
A.4. Database variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
| Database name used for connections to the PostgreSQL database server. | Optional |
| |
|
| The firewall zone where PostgreSQL related firewall rules are applied. This controls which networks can access PostgreSQL based on the zone’s trust level. | Optional |
RPM = no default set. Container = |
|
|
Maximum number of concurrent connections to the database if you are using an installer-managed database. | Optional |
|
|
Password for the PostgreSQL admin user. |
Required if using | ||
|
| Path to the PostgreSQL SSL/TLS certificate file. | Optional | |
|
| Path to the PostgreSQL SSL/TLS key file. | Optional | |
|
| Controls whether SSL/TLS is enabled or disabled for the PostgreSQL database. | Optional |
|
|
Username for the PostgreSQL admin user. | Optional |
| |
| Memory allocation available (in MB) for caching data. | Optional | ||
|
Controls whether or not to keep databases during uninstall. | Optional |
| |
| Destination for server log output. | Optional |
| |
| The algorithm for encrypting passwords. | Optional |
| |
|
| Port number for the PostgreSQL database. | Optional |
|
| Memory allocation (in MB) for shared memory buffers. | Optional | ||
|
Denote whether the PostgreSQL provided certificate files are local to the installation program ( | Optional |
|
A.5. Event-Driven Ansible controller variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
|
| Number of workers used for ansible-rulebook activation pods in Event-Driven Ansible. | Optional |
RPM = (# of cores or threads) * 2 + 1. Container = |
|
| Email address used by Django for the admin user for Event-Driven Ansible. | Optional |
|
|
|
Event-Driven Ansible administrator password. Use of special characters for this variable is limited. The password can include any printable ASCII character except | Required | |
|
| Username used to identify and create the administrator user in Event-Driven Ansible. | Optional |
|
| Number of workers for handling the API served through Gunicorn on worker nodes. | Optional |
| |
|
Denote whether the cache cert sources are local to the installation program ( | Optional |
| |
|
Controls whether or not to regenerate Event-Driven Ansible client certificates for the platform cache. Set to | Optional |
| |
|
| Number of workers used in Event-Driven Ansible for application work. | Optional | Number of cores or threads |
|
|
Controls whether HTTP Strict Transport Security (HSTS) is enabled or disabled for Event-Driven Ansible. Set this variable to | Optional |
|
|
|
Controls whether HTTPS is enabled or disabled for Event-Driven Ansible. Set this variable to | Optional |
|
|
| API prefix path used for Event-Driven Ansible event-stream through platform gateway. | Optional |
|
|
| The firewall zone where Event-Driven Ansible related firewall rules are applied. This controls which networks can access Event-Driven Ansible based on the zone’s trust level. | Optional |
RPM = no default set. Container = |
| Number of workers for handling event streaming for Event-Driven Ansible. | Optional |
| |
|
| Number of workers for handling the API served through Gunicorn. | Optional | (Number of cores or threads) * 2 + 1 |
|
| Port number that Event-Driven Ansible listens on for HTTP requests. | Optional |
RPM = |
|
| Port number that Event-Driven Ansible listens on for HTTPS requests. | Optional |
RPM = |
|
| Number of maximum activations running concurrently per node. This is an integer that must be greater than 0. | Optional |
|
|
Denote whether the web cert sources are local to the installation program ( | Optional |
| |
|
|
Controls whether client certificate authentication is enabled or disabled on the Event-Driven Ansible PostgreSQL database. Set this variable to | Optional |
|
|
| Name of the PostgreSQL database used by Event-Driven Ansible. | Optional |
RPM = |
|
| Hostname of the PostgreSQL database used by Event-Driven Ansible. | Required | |
|
|
Password for the Event-Driven Ansible PostgreSQL database user. Use of special characters for this variable is limited. The | Required if not using client certificate authentication. | |
|
| Port number for the PostgreSQL database used by Event-Driven Ansible. | Optional |
|
|
|
Determines the level of encryption and authentication for client server connections. Valid options include | Optional |
|
|
| Username for the Event-Driven Ansible PostgreSQL database user. | Optional |
RPM = |
|
| Path to the PostgreSQL SSL/TLS certificate file for Event-Driven Ansible. | Required if using client certificate authentication. | |
|
| Path to the PostgreSQL SSL/TLS key file for Event-Driven Ansible. | Required if using client certificate authentication. | |
|
Denote whether the PostgreSQL client cert sources are local to the installation program ( | Optional |
| |
|
|
URL for connecting to the event stream. The URL must start with the | Optional | |
|
| Hostname of the Redis host used by Event-Driven Ansible. | Optional |
First node in the |
|
| Password for Event-Driven Ansible Redis. | Optional | Randomly generated string |
|
| Port number for the Redis host for Event-Driven Ansible. | Optional |
RPM = The value defined in platform gateway’s implementation ( |
|
| Username for Event-Driven Ansible Redis. | Optional |
|
|
| Secret key value used by Event-Driven Ansible to sign and encrypt data. | Optional | |
|
| Path to the SSL/TLS certificate file for Event-Driven Ansible. | Optional | |
|
| Path to the SSL/TLS key file for Event-Driven Ansible. | Optional | |
|
|
Denote whether the Event-Driven Ansible provided certificate files are local to the installation program ( | Optional |
|
|
List of host addresses in the form: | Optional |
| |
|
| List of additional NGINX headers to add to Event-Driven Ansible’s NGINX configuration. | Optional |
|
|
Controls whether or not to perform SSL verification for the Daphne WebSocket used by Podman to communicate from the pod to the host. Set to | Optional |
| |
|
|
Event-Driven Ansible node type. Valid options include | Optional |
|
|
Controls whether debug mode is enabled or disabled for Event-Driven Ansible. Set to | Optional |
| |
| Defines additional settings for use by Event-Driven Ansible during installation. For example: eda_extra_settings: - setting: RULEBOOK_READINESS_TIMEOUT_SECONDS value: 120 | Optional |
| |
| Maximum allowed size for data sent to Event-Driven Ansible through NGINX. | Optional |
| |
| Maximum duration (in seconds) that HTTP Strict Transport Security (HSTS) is enforced for Event-Driven Ansible. | Optional |
| |
|
| Protocols that Event-Driven Ansible supports when handling HTTPS traffic. | Optional |
RPM = |
| UNIX socket used by Event-Driven Ansible to connect to the PostgreSQL database. | Optional | ||
|
| Controls whether TLS is enabled or disabled for Event-Driven Ansible Redis. Set this variable to true to disable TLS. | Optional |
|
| Path to the Event-Driven Ansible Redis certificate file. | Optional | ||
| Path to the Event-Driven Ansible Redis key file. | Optional | ||
| List of plugins that are allowed to run within Event-Driven Ansible. For more information about the usage of this variable, see Adding a safe plugin variable to Event-Driven Ansible controller. | Optional |
|
A.6. General variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
|
| Path to the user provided CA certificate file used to generate SSL/TLS certificates for all Ansible Automation Platform services. For more information, see Optional: Using custom TLS certificates. | Optional | |
|
|
Denote whether the CA certificate files are local to the installation program ( | Optional |
|
| Bit size of the internally managed CA certificate private key. | Optional |
| |
|
|
Path to the key file for the CA certificate provided in | Optional | |
| Cipher used for signing the internally managed CA certificate private key. | Optional |
| |
| Denotes whether or not to re-initiate the internally managed CA certificate key pair. | Optional |
| |
| Bit size of the component key pair managed by the internal CA. | Optional |
| |
| Denotes whether or not to re-initiate the component key pair managed by the internal CA. | Optional |
| |
|
A list of additional SAN records for signing a service. Assign these to components in the inventory file as host variables rather than group or all variables. All strings must also contain their corresponding SAN option prefix such as | Optional |
| |
|
Directory local to | Optional |
The value defined in | |
|
| Directory used to store backup files. | Optional |
RPM = |
| Prefix used for the file backup name for the final backup file. | Optional |
| |
|
|
Controls whether or not to perform an offline or bundled installation. Set this variable to | Optional |
|
|
| Path to the bundle directory used when performing a bundle install. |
Required if |
RPM = |
|
| Path to the custom CA certificate file. This is required if any of the TLS certificates you manually provided are signed by a custom CA. For more information, see Optional: Using custom TLS certificates. | Optional | |
|
The default install registers the node to the Red Hat Insights for Red Hat Ansible Automation Platform for the Red Hat Ansible Automation Platform Service if the node is registered with Subscription Manager. Set to | Optional |
| |
|
|
Password credential for access to the registry source defined in |
RPM = Required if you need a password to access | |
|
| URL of the registry source from which to pull execution environment images. | Optional |
|
|
|
Username credential for access to the registry source defined in |
RPM = Required if you need a password to access | |
|
| Controls whether SSL/TLS certificate verification is enabled or disabled when making HTTPS requests. | Optional |
|
| Path to the tar file used for the platform restore. | Optional |
| |
| Path prefix for the staged restore components. | Optional |
| |
|
|
Used if the machine running the installation program can only route to the target host through a specific URL. For example, if you use short names in your inventory, but the node running the installation program can only resolve that host by using a FQDN. If | Optional | |
|
Passphrase used to decrypt the key provided in | Optional | ||
| Compression software to use for compressing container images. | Optional |
| |
|
Controls whether or not to keep container images when uninstalling Ansible Automation Platform. Set to | Optional |
| |
|
Controls whether or not to pull newer container images during installation. Set to | Optional |
| |
| The firewall zone where Performance Co-Pilot related firewall rules are applied. This controls which networks can access Performance Co-Pilot based on the zone’s trust level. | Optional | public | |
|
Set whether or not to use registry authentication. When this variable is set to true, | Optional |
| |
| Ansible Automation Platform registry namespace. | Optional |
| |
| RHEL registry namespace. | Optional |
| |
|
Controls at the global level whether the filesystem-related backup files will be compressed before being sent to the host to run the backup operation. If set to true, a
This functionality can be controlled at the component level using the | Optional |
| |
|
Enables or disables archive compression on a component level by specifying the component in For example:
This functionality can be controlled at the global level using the | Optional |
| |
|
Controls at the global level whether the database-related backup files will be compressed before being sent to the host to run the backup operation. This functionality can be controlled at the component level using the | Optional |
| |
|
Enables or disables archive compression on a database level by specifying the component in For example:
This functionality can be controlled at the global level using the | Optional |
|
A.7. Image variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
| Additional container images to pull from the configured container registry during deployment. | Optional |
| |
| Container image for automation controller. | Optional |
| |
| Additional decision environment container images to pull from the configured container registry during deployment. | Optional |
| |
| Supported decision environment container image. | Optional |
| |
| Backend container image for Event-Driven Ansible. | Optional |
| |
| Front-end container image for Event-Driven Ansible. | Optional |
| |
| Additional execution environment container images to pull from the configured container registry during deployment. | Optional |
| |
| Minimal execution environment container image. | Optional |
| |
| Supported execution environment container image. | Optional |
| |
| Container image for platform gateway. | Optional |
| |
| Container image for platform gateway proxy. | Optional |
| |
| Backend container image for automation hub. | Optional |
| |
| Front-end container image for automation hub. | Optional |
| |
| Container image for Performance Co-Pilot. | Optional |
| |
| Container image for PostgreSQL. | Optional |
| |
| Container image for receptor. | Optional |
| |
| Container image for Redis. | Optional |
|
A.8. Platform gateway variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
|
| Email address used by Django for the admin user for platform gateway. | Optional |
|
|
|
Platform gateway administrator password. Use of special characters for this variable is limited. The password can include any printable ASCII character except | Required | |
|
| Username used to identify and create the administrator user in platform gateway. | Optional |
|
|
| Path to the platform gateway Redis certificate file. | Optional | |
|
| Path to the platform gateway Redis key file. | Optional | |
|
Denote whether the cache client certificate files are local to the installation program ( | Optional |
The value defined in | |
|
Controls whether or not to regenerate platform gateway client certificates for the platform cache. Set to | Optional |
| |
|
| Port number for the platform gateway control plane. | Optional |
|
|
|
Controls whether HTTP Strict Transport Security (HSTS) is enabled or disabled for platform gateway. Set this variable to | Optional |
|
|
|
Controls whether HTTPS is enabled or disabled for platform gateway. Set this variable to | Optional |
RPM = The value defined in |
|
| The firewall zone where platform gateway related firewall rules are applied. This controls which networks can access platform gateway based on the zone’s trust level. | Optional | RPM = no default set. Container = 'public'. |
|
| Timeout duration (in seconds) for requests made to the gRPC service on platform gateway. | Optional |
|
|
| Maximum number of threads that each gRPC server process can create to handle requests on platform gateway. | Optional |
|
|
| Number of processes for handling gRPC requests on platform gateway. | Optional |
|
|
| Port number that platform gateway listens on for HTTP requests. | Optional |
RPM = |
|
| Port number that platform gateway listens on for HTTPS requests. | Optional |
RPM = |
|
|
URL of the main instance of platform gateway that clients connect to. Use if you are performing a clustered deployment and you need to use the URL of the load balancer instead of the component’s server. The URL must start with | Optional | |
|
Denote whether the web cert sources are local to the installation program ( | Optional |
The value defined in | |
|
|
Controls whether client certificate authentication is enabled or disabled on the platform gateway PostgreSQL database. Set this variable to | Optional |
|
|
| Name of the PostgreSQL database used by platform gateway. | Optional |
RPM = |
|
| Hostname of the PostgreSQL database used by platform gateway. | Required | |
|
|
Password for the platform gateway PostgreSQL database user. Use of special characters for this variable is limited. The | Optional | |
|
| Port number for the PostgreSQL database used by platform gateway. | Optional |
|
|
|
Controls the SSL mode to use when platform gateway connects to the PostgreSQL database. Valid options include | Optional |
|
|
| Username for the platform gateway PostgreSQL database user. | Optional |
RPM = |
|
| Path to the PostgreSQL SSL/TLS certificate file for platform gateway. | Required if using client certificate authentication. | |
|
| Path to the PostgreSQL SSL/TLS key file for platform gateway. | Required if using client certificate authentication. | |
|
Denote whether the PostgreSQL client cert sources are local to the installation program ( | Optional |
The value defined in | |
|
| Hostname of the Redis host used by platform gateway. | Optional |
First node in the |
|
| Password for platform gateway Redis. | Optional | Randomly generated string. |
|
| Username for platform gateway Redis. | Optional |
|
|
| Secret key value used by platform gateway to sign and encrypt data. | Optional | |
| Denotes whether or not to verify platform gateway’s web certificates when making calls from platform gateway to itself during installation. Set to false to disable web certificate verification. | Optional |
| |
|
| Path to the SSL/TLS certificate file for platform gateway. | Optional | |
|
| Path to the SSL/TLS key file for platform gateway. | Optional | |
|
|
Denote whether the platform gateway provided certificate files are local to the installation program ( | Optional |
|
|
| List of additional NGINX headers to add to platform gateway’s NGINX configuration. | Optional |
|
|
|
Controls whether or not HTTPS is disabled when accessing the platform UI. Set to | Optional |
RPM = The value defined in |
|
| Port number on which the Envoy proxy listens for incoming HTTP connections. | Optional |
|
|
| Port number on which the Envoy proxy listens for incoming HTTPS connections. | Optional |
|
|
| Protocols that platform gateway will support when handling HTTPS traffic. | Optional |
RPM = |
|
|
Controls whether TLS is enabled or disabled for platform gateway Redis. Set this variable to | Optional |
|
|
| Port number for the Redis host for platform gateway. | Optional |
|
| Defines additional settings for use by platform gateway during installation. For example: gateway_extra_settings: - setting: OAUTH2_PROVIDER['ACCESS_TOKEN_EXPIRE_SECONDS'] value: 600 | Optional |
| |
| Maximum allowed size for data sent to platform gateway through NGINX. | Optional |
| |
| Maximum duration (in seconds) that HTTP Strict Transport Security (HSTS) is enforced for platform gateway. | Optional |
| |
|
Number of requests | Optional |
|
A.9. Receptor variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
|
The directory where receptor stores its runtime data and local artifacts. | Optional |
| |
|
| Port number that receptor listens on for incoming connections from other receptor nodes. | Optional |
|
|
| Protocol that receptor will support when handling traffic. | Optional |
|
|
|
Controls the verbosity of logging for receptor. | Optional |
|
|
Controls whether TLS is enabled or disabled for receptor. Set this variable to | Optional |
| |
See |
|
For the
For the
| Optional |
For the |
See |
| Used to indicate which nodes a specific host connects to. Wherever this variable is defined, an outbound connection to the specific host is established. The value must be a comma-separated list of hostnames. Do not use inventory group names.
This is resolved into a set of hosts that is used to construct the For example usage, see Adding execution nodes. | Optional |
|
|
Controls whether signing of communications between receptor nodes is enabled or disabled. | Optional |
| |
|
Controls whether TLS is enabled or disabled for receptor. | Optional |
| |
| The firewall zone where receptor related firewall rules are applied. This controls which networks can access receptor based on the zone’s trust level. | Optional |
| |
|
Controls whether or not receptor only accepts connections that use TLS 1.3 or higher. | Optional |
| |
| Path to the private key used by receptor to sign communications with other receptor nodes in the network. | Optional | ||
| Path to the public key used by receptor to sign communications with other receptor nodes in the network. | Optional | ||
|
Denote whether the receptor signing files are local to the installation program ( | Optional |
| |
| Path to the TLS certificate file for receptor. | Optional | ||
| Path to the TLS key file for receptor. | Optional | ||
|
Denote whether the receptor provided certificate files are local to the installation program ( | Optional |
|
A.10. Redis variables
RPM variable name | Container variable name | Description | Required or optional | Default |
---|---|---|---|---|
|
|
The IPv4 address used by the Redis cluster to identify each host in the cluster. When defining hosts in the | Optional | RPM = Discovered IPv4 address from Ansible facts. If IPv4 address is not available, IPv6 address is used. Container = Discovered IPv4 address from Ansible facts. |
|
Controls whether mTLS is enabled or disabled for Redis. Set this variable to | Optional |
| |
|
| The firewall zone where Redis related firewall rules are applied. This controls which networks can access Redis based on the zone’s trust level. | Optional |
RPM = no default set. Container = |
|
Hostname used by the Redis cluster when identifying and routing the host. By default | Optional |
The value defined in | |
|
|
The Redis mode to use for your Ansible Automation Platform installation. Valid options include: | Optional |
|
| Denotes whether or not to regenerate the Ansible Automation Platform managed TLS key pair for Redis. | Optional |
| |
|
| Path to the Redis server TLS certificate. | Optional | |
|
Denote whether the Redis provided certificate files are local to the installation program ( | Optional |
| |
|
| Path to the Redis server TLS certificate key. | Optional |