Most users will not need to use this feature. See `developing_plugins` for more details
error_on_undefined_vars
=======================
On by default since Ansible 1.3, this causes ansible to fail steps that reference variable names that are likely
typoed::
#error_on_undefined_vars=True
If set to False, any '{{ template_expression }}' that contains undefined variables will be rendered in a template
or ansible action line exactly as written.
executable
==========
This indicates the command to use to spawn a shell under a sudo environment. Users may need to change this in
rare instances to /bin/bash in rare instances wehn sudo is constrained, but in most cases it may be left as is::
#executable = /bin/bash
forks
=====
This is the default number of parallel processes to spawn when communicating with remote hosts. Since Ansible 1.3,
the fork number is automatically limited to the number of possible hosts, so this is really a limit of how much
network and CPU load you think you can handle. Many users may set this to 50, some set it to 500 or more. If you
have a large number of hosts, higher values will make actions across all of those hosts complete faster. The default
is very very conservative::
forks=5
pattern
=======
This is the default group of hosts to talk to in a playbook if no "hosts:" stanza is supplied. The default is to talk
to all hosts. You may wish to change this to protect yourself from surprises::
hosts=*
Note that /usr/bin/ansible always requires a host pattern and does not use this setting, only /usr/bin/ansible-playbook.
poll_interval
=============
For asynchronous tasks in Ansible (covered in `playbooks_async`), this is how often to check back on the status of those
tasks when an explicit poll interval is not supplied. The default is a reasonably moderate 15 seconds which is a tradeoff
between checking in frequently and providing a quick turnaround when something may have completed::
poll_interval=15
hash_behavior
=============
Ansible by default will override variables in specific precedence orders, as described in `playbooks_variables`. When a variable
of higher precedence wins, it will replace the other value.
Some users prefer that variables that are hashes (aka 'dictionaries' in Python terms) are merged together. This setting is called 'merge'. This is not the default behavior and it does not affect variables whose values are scalars (integers, strings) or
arrays. We generally recommend not using this setting unless you think you have an absolute need for it, and playbooks in the
official examples repos do not use this setting::
#hash_behavior=replace
The valid values are either 'replace' (the default) or 'merge'.
hostfile
========
This is the default location of the inventory file, script, or directory that Ansible will use to determine what hosts it has available
to talk to::
hostfile = /etc/ansible/hosts
host_key_checking
=================
As described in `intro_gettingstarted`, host key checking is on by default in Ansible 1.3 and later. If you understand the
implications and wish to disable it, you may do so here by setting the value to False::
host_key_checking=True
filter_plugins
==============
This is a developer-centric feature that allows low-level extensions around Ansible to be loaded from