ansible.posix.skippy callback – Ansible screen output that ignores skipped status
Note
This callback plugin is part of the ansible.posix collection (version 1.6.2).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install ansible.posix.
You need further requirements to be able to use this callback plugin,
see Requirements for details.
To use it in a playbook, specify: ansible.posix.skippy.
DEPRECATED
- Removed in:
- major release after 2024-12-05 
- Why:
- The ‘default’ callback plugin now supports this functionality 
- Alternative:
- ‘default’ callback plugin with ‘display_skipped_hosts = no’ option 
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 callback does the same as the default except it does not output skipped host/task/item status 
Requirements
The below requirements are needed on the local controller node that executes this callback.
- set as main display callback 
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 rather than 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: 
 | |
| 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 starts 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: 
 | 
Note
Configuration entries listed above for each entry type (Ansible variable, environment variable, and so on) 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. The entry types are also ordered by precedence from low to high priority order. For example, an ansible.cfg entry (further up in the list) is overwritten by an Ansible variable (further down in the list).
Status
- This callback will be removed in a major release after 2024-12-05. [deprecated] 
- For more information see DEPRECATED. 
