x/browbeat
Code Issues Proposed changes
browbeat/ansible/check
History
Chuck Short 6d03698faa Clean up linter 
Enable ANSIBLE0010, package installs should
not use latest. Package installs should use state=present with
or without a version.

Change-Id: Id9868d0170fcf715be473d121f9db809f6c7d528
Signed-off-by: Chuck Short <chucks@redhat.com>
2018-08-16 09:02:50 -04:00
..
group_vars
Correct bug report save location
2016-09-14 15:03:48 -04:00
roles
Clean up linter
2018-08-16 09:02:50 -04: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

README.rst

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.