In particular, users may wish to raise the ControlPersist time to encourage performance. Module documentation is not edited directly, but is generated from the source code for the modules. 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. Type: boolean Default: True Version Added: 2. A value of 30 minutes may be appropriate. See the Jinja2 documentation for details. Use the debugger keyword for more flexibility.
For help in developing on modules, should you be so inclined, please read , and. This option can be useful for those wishing to save fact gathering time. These headers will contain the name: field from the task if you specified one. Equivalent to multiple —vault-id args. You can also control this at the task level with the module option warn. One example are docker mounted files, they cannot be updated atomically and can only be done in an unsafe manner.
E root sudo to root. This option is usually not required, it might be useful when access to system ssh is restricted, or when using ssh wrappers to connect to remote hosts. Type: boolean Default: False Version Added: 2. The debugger defaults to activating when a task is failed on unreachable. See the module documentation for specifics. This can result in a very significant performance improvement when enabled. .
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 In version 2. However this conflicts with privilege escalation become. Relative paths for configuration You can specify a relative path for many configuration options. It does not apply to user defined M setup tasks. This setting allows to return to that behaviour. This may be used to log activity from the command line, send notifications, and so on. If touch new in 1.
You can have many other callbacks, but just one can be in charge of stdout. You can also control this at the task level with the module option warn. The bottom option follows the 2. Type: boolean Default: False Version Added: 2. Type: boolean Default: False Version Added: 1. Will accept absolute, relative and nonexisting paths. By default Ansible will override variables in specific precedence orders, as described in Variables.
The all option examines from the first parent to the current playbook. Now all strategy plugins can inherit this behavior. Type: boolean Default: False Version Added: 2. This can also be set per play or on the command line. Expect the default to change in version 2. These warnings can be silenced by adjusting this setting to False. By default Ansible will override variables in specific precedence orders, as described in Variables.
This does not affect user defined tasks that use the M setup module. The all option examines from the first parent to the current playbook. In particular, users may wish to raise the ControlPersist time to encourage performance. When empty logging is disabled. When not set it will let Jinja2 decide. 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.
Vault-ids are tried in order. This can result in a very significant performance improvement when enabled. Type: boolean Default: False Version Added: 2. 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 settingIn version 2. If path is a directory, it is copied recursively. Type: boolean Default: True Version Added: 1.
See Handlers and Failure for more details. 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. The fallback behavior will issue a warning that the interpreter should be set explicitly since interpreters installed later may change which one is used. However this conflicts with privilege escalation become. This was introduced as a way to reset role variables to default values if a role is used more than once in a playbook. In most of those cases, the correct fix is to modify the mount options of the filesystem so the files and directories are readable and writable by the users and groups running Ansible but closed to others.
This may be used to log activity from the command line, send notifications, and so on. Type: boolean Default: False Version Added: 2. The value will be limited by the existing hard limit. Use % directory s to indicate where to use the control dir path setting. All discovery modes employ a lookup table to use the included system Python on distributions known to include one , falling back to a fixed ordered list of well-known Python interpreter locations if a platform-specific default is not available. Type: string Default: warn Version Added: 2.