2020-01-14 23:15:13 +00:00
|
|
|
---
|
|
|
|
|
title: Documentation
|
|
|
|
|
---
|
|
|
|
|
|
2020-01-27 12:54:31 +00:00
|
|
|
[](https://cloud.drone.io/xoxys/ansible-later)
|
|
|
|
|
[](https://hub.docker.com/r/xoxys/ansible-later)
|
|
|
|
|
[](https://pypi.org/project/ansible-later/)
|
|
|
|
|
[](https://pypi.org/project/ansible-later/)
|
|
|
|
|
[](https://pypi.org/project/ansible-later/)
|
2020-01-27 12:59:51 +00:00
|
|
|
[](https://codecov.io/gh/xoxys/ansible-later)
|
2020-01-27 12:54:31 +00:00
|
|
|
[](LICENSE)
|
2020-01-14 23:15:13 +00:00
|
|
|
|
|
|
|
|
This is a fork of Will Thames [ansible-review](https://github.com/willthames/ansible-review) so credits goes to him
|
|
|
|
|
for his work on ansible-review and ansible-lint.
|
|
|
|
|
|
2020-01-27 12:54:31 +00:00
|
|
|
_ansible-later_ is a best pratice scanner and linting tool. In most cases, if you write ansibel roles in a team,
|
2020-01-14 23:15:13 +00:00
|
|
|
it helps to have a coding or best practice guideline in place. This will make ansible roles more readable for all
|
|
|
|
|
maintainers and can reduce the troubleshooting time.
|
|
|
|
|
|
2020-01-27 12:54:31 +00:00
|
|
|
_ansible-later_ does __not__ ensure that your role will work as expected. For Deployment test you can use other tools
|
2020-01-14 23:15:13 +00:00
|
|
|
like [molecule](https://github.com/ansible/molecule).
|
