browbeat/ansible/check
Chuck Short 959bed59a5 Enable linter test for ANSIBLE0013
Use shell only shell functionality is required.
The shell functionality should only be used when piping, redirecting or
chaining commands.

Change-Id: Icb9b1dd5ea22a2af895a87a9fa2cc1b9a488ac0c
Signed-off-by: Chuck Short <chucks@redhat.com>
2018-08-10 14:28:36 +00:00
..
group_vars Correct bug report save location 2016-09-14 15:03:48 -04:00
roles Enable linter test for ANSIBLE0013 2018-08-10 14:28:36 +00:00
templates Implement Suggestions 2016-08-31 15:14:25 -04:00
browbeat-example-bug_report.log Update example bug report 2016-10-10 11:25:11 -04:00
README.rst Update example bug report 2016-10-10 11:25:11 -04:00
site.yml Update tox.ini with Ansible linting and Browbeat config linting 2017-03-29 07:35:34 -04:00

Browbeat Ansible Checks

The Browbeat Ansible checks playbook will scan a given deployment to check for known configuration issues.

Output from Checks

Once the Checks playbook completes there will be a report generated in the browbeat results directory.

bug_report.log

This will contain each of the hosts that were scanned, and their known issues. Some of the issues will have BZ's associated with them, use the BZ link to learn more about the bug, and how it can impact your deployment. There will be Checks that do not have a BZ associated, these are simply suggestions.