Executing ansible playbooks emit alot of (per TASK) messages on the console.
This is an unfortunate side-effect of using ansible based automation which can
lead to:
- difficulties isolating msgs related to debugging failures
- massive and difficult to read console logs
This RFE requests that the console messaging architecture of this automation investigate ways to quiet the (unnecessary) TASK messages and reduce console messages to logging progress through the execution phases of the playbook.
Perhaps a DEBUG env var could re-enable the noisy (default) Ansible behavior.
Executing ansible playbooks emit alot of (per TASK) messages on the console.
This is an unfortunate side-effect of using ansible based automation which can
lead to:
This RFE requests that the console messaging architecture of this automation investigate ways to quiet the (unnecessary) TASK messages and reduce console messages to logging progress through the execution phases of the playbook.
Perhaps a DEBUG env var could re-enable the noisy (default) Ansible behavior.