- This setting controls the timeout for the accelerated daemon, as measured in minutes. The default daemon timeout is 30 minutes.
- Prior to 1.6, the timeout was hard-coded from the time of the daemon’s launch.
- "Prior to 1.6, the timeout was hard-coded from the time of the daemon's launch."
- For version 1.6+, the timeout is now based on the last activity to the daemon and is configurable via this option.
env:[{name:ACCELERATE_DAEMON_TIMEOUT}]
ini:
@ -158,8 +158,8 @@ ANSIBLE_PIPELINING:
- Pipelining, if supported by the connection plugin, reduces the number of network operations required to execute a module on the remote server,
by executing many Ansible modules without actual file transfer.
- This can result in a very significant performance improvement when enabled.
- However this conflicts with privilege escalation (become). For example, when using “sudo:” operations you must first
disable ‘requiretty’ in /etc/sudoers on all managed hosts, which is why it is disabled by default.
- "However this conflicts with privilege escalation (become). For example, when using 'sudo:' operations you must first
disable 'requiretty' in /etc/sudoers on all managed hosts, which is why it is disabled by default."
env:[{name:ANSIBLE_PIPELINING}]
ini:
- {key: pipelining, section:connection}
@ -217,7 +217,7 @@ ANSIBLE_SSH_PIPELINING:
- Pipelining reduces the number of SSH operations required to execute a module on the remote server,
by executing many Ansible modules without actual file transfer.
- This can result in a very significant performance improvement when enabled.
- However this conflicts with privilege escalation (become). For example, when using “sudo:” operations you must first disable ‘requiretty’ in /etc/sudoers on all managed hosts, which is why it is disabled by default.
- "However this conflicts with privilege escalation (become). For example, when using 'sudo:' operations you must first disable 'requiretty' in /etc/sudoers on all managed hosts, which is why it is disabled by default."
env:[{name:ANSIBLE_SSH_PIPELINING}]
ini:
- {key: pipelining, section:ssh_connection}
@ -406,8 +406,8 @@ DEFAULT_ALLOW_UNSAFE_LOOKUPS:
name:Allow unsafe lookups
default:False
description:
- When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup(‘foo’)}}`` or as a loop as with_foo)
to return data that is not marked “unsafe”.
- "When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo)
to return data that is not marked 'unsafe'."
- By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language,
as this could represent a security risk. This option is provided to allow for backwards-compatibility,
however users should first consider adding allow_unsafe=True to any lookups which may be expected to contain data which may be run
@ -489,7 +489,7 @@ DEFAULT_BECOME_METHOD:
DEFAULT_BECOME_EXE:
name:Choose 'become' executable
default:~
description:'executable to use for privilege escalation, otherwise Ansible will depend on PATh'
description:'executable to use for privilege escalation, otherwise Ansible will depend on PATH'
env:[{name:ANSIBLE_BECOME_EXE}]
ini:
- {key: become_exe, section:privilege_escalation}
@ -538,8 +538,8 @@ DEFAULT_CALLBACK_WHITELIST:
name:Callback Whitelist
default:[]
description:
- List of whitelisted callbacks, not all callbacks need whitelisting,
but many of those shipped with Ansible do as we don't want them activated by default.
- "List of whitelisted callbacks, not all callbacks need whitelisting,
but many of those shipped with Ansible do as we don't want them activated by default."
env:[{name:ANSIBLE_CALLBACK_WHITELIST}]
ini:
- {key: callback_whitelist, section:defaults}
@ -566,8 +566,8 @@ DEFAULT_EXECUTABLE:
name:Target shell executable
default:/bin/sh
description:
- This indicates the command to use to spawn a shell under for Ansible's execution needs on a target.
Users may need to change this in rare instances when shell usage is constrained, but in most cases it may be left as is.
- "This indicates the command to use to spawn a shell under for Ansible's execution needs on a target.
Users may need to change this in rare instances when shell usage is constrained, but in most cases it may be left as is."
env:[{name:ANSIBLE_EXECUTABLE}]
ini:
- {key: executable, section:defaults}
@ -575,9 +575,9 @@ DEFAULT_FACT_PATH:
name:local fact path
default:~
description:
- This option allows you to globally configure a custom path for 'local_facts' for the implied M(setup) task when using fact gathering.
- "This option allows you to globally configure a custom path for 'local_facts' for the implied M(setup) task when using fact gathering."
- "If not set, it will fallback to the default from the M(setup) module: ``/etc/ansible/facts.d``."
- This does **not ** affect user defined tasks that use the M(setup) module.
- "This does **not** affect user defined tasks that use the M(setup) module."
env:[{name:ANSIBLE_FACT_PATH}]
ini:
- {key: fact_path, section:defaults}
@ -616,11 +616,11 @@ DEFAULT_GATHERING:
default:'implicit'
description:
- This setting controls the default policy of fact gathering (facts discovered about remote systems).
- "When ‘implicit’ (the default), the cache plugin will be ignored and facts will be gathered per play unless ‘gather_facts: False’ is set."
- When ‘explicit’ the inverse is true, facts will not be gathered unless directly requested in the play.
- The ‘smart’ value means each new host that has no facts discovered will be scanned,
but if the same host is addressed in multiple plays it will not be contacted again in the playbook run.
- This option can be useful for those wishing to save fact gathering time. Both ‘smart’ and ‘explicit’ will use the cache plugin.
- "When 'implicit' (the default), the cache plugin will be ignored and facts will be gathered per play unless 'gather_facts: False' is set."
- "When 'explicit' the inverse is true, facts will not be gathered unless directly requested in the play."
- "The 'smart' value means each new host that has no facts discovered will be scanned,
but if the same host is addressed in multiple plays it will not be contacted again in the playbook run."
- "This option can be useful for those wishing to save fact gathering time. Both 'smart' and 'explicit' will use the cache plugin."
env:[{name:ANSIBLE_GATHERING}]
ini:
- key:gathering
@ -633,7 +633,7 @@ DEFAULT_GATHER_SUBSET:
description:
- Set the `gather_subset` option for the M(setup) task in the implicit fact gathering.
See the module documentation for specifics.
- It does **not** apply to user defined M(setup) tasks.
- "It does **not** apply to user defined M(setup) tasks."
env:[{name:ANSIBLE_GATHER_SUBSET}]
ini:
- key:gather_subset
@ -644,7 +644,7 @@ DEFAULT_GATHER_TIMEOUT:
default:10
description:
- Set the timeout in seconds for the implicit fact gathering.
- It does **not** apply to user defined M(setup) tasks.
- "It does **not** apply to user defined M(setup) tasks."
- Ansible can optimise actions that call modules that support list parameters when using with_ looping.
- Ansible can optimise actions that call modules that support list parameters when using ``with_`` looping.
Instead of calling the module once for each item, the module is called once with the full list.
- The default value for this setting is only for certain package managers, but it can be used for any module
- Currently, this is only supported for modules that have a name or pkg parameter, and only when the item is the only thing being passed to the parameter.
- When True, this causes ansible templating to fail steps that reference variable names that are likely typoed.
- Otherwise, any ‘{{ template_expression }}’ that contains undefined variables will be rendered in a template or ansible action line exactly as written.
- "Otherwise, any '{{ template_expression }}' that contains undefined variables will be rendered in a template or ansible action line exactly as written."
Adrian Likins
7 years ago
committed by