ansible.builtin.default callback – default Ansible screen output
Note
This callback plugin is part of ansible-core
and included in all Ansible
installations. In most cases, you can use the short
plugin name
default
.
However, we recommend you use the Fully Qualified Collection Name (FQCN) ansible.builtin.default
for easy linking to the
plugin documentation and to avoid conflicting with other collections that may have
the same callback plugin name.
Callback plugin
This plugin is a stdout callback. You can use only use one stdout callback at a time. Additional aggregate or notification callbacks can be enabled though. See Callback plugins for more information on callback plugins.
Synopsis
This is the default output callback for ansible-playbook.
Requirements
The below requirements are needed on the local controller node that executes this callback.
set as stdout in configuration
Parameters
Parameter |
Comments |
---|---|
Toggle to control displaying markers when running in check mode. The markers are Choices:
Configuration:
|
|
Toggle to control whether failed and unreachable tasks are displayed to STDERR (vs. STDOUT) Choices:
Configuration:
|
|
Toggle to control displaying ‘ok’ task/host results in a task Choices:
Configuration:
|
|
Toggle to control displaying skipped task/host results in a task Choices:
Configuration:
|
|
Configure the result format to be more readable When Setting this option to When set to Choices:
Configuration:
|
|
Define the task result format used in the callback output. These formats do not cause the callback to emit valid JSON or YAML formats. The output contains these formats interspersed with other non-machine parsable data. Choices:
Configuration:
|
|
This adds the custom stats set via the set_stats plugin to the play recap Choices:
Configuration:
|
|
This adds output that shows when a task is started to execute for each host Choices:
Configuration:
|
|
When a task fails, display the path to the file containing the failed task and the line number. This information is displayed automatically for every task when running with Choices:
Configuration:
|
Hint
Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.