mirror of
https://github.com/thegeeklab/ansible-later.git
synced 2024-11-22 21:00:44 +00:00
20 lines
2.1 KiB
Markdown
20 lines
2.1 KiB
Markdown
---
|
|
title: Documentation
|
|
---
|
|
|
|
[](https://ci.thegeeklab.de/repos/thegeeklab/ansible-later)
|
|
[](https://hub.docker.com/r/thegeeklab/ansible-later)
|
|
[](https://quay.io/repository/thegeeklab/ansible-later)
|
|
[](https://pypi.org/project/ansible-later/)
|
|
[](https://pypi.org/project/ansible-later/)
|
|
[](https://pypi.org/project/ansible-later/)
|
|
[](https://codecov.io/gh/thegeeklab/ansible-later)
|
|
[](https://github.com/thegeeklab/ansible-later/graphs/contributors)
|
|
[](https://github.com/thegeeklab/ansible-later)
|
|
[](https://github.com/thegeeklab/ansible-later/blob/main/LICENSE)
|
|
|
|
ansible-later is a best practice scanner and linting tool. In most cases, if you write Ansible roles in a team, 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. While ansible-later aims to be a fast and easy to use linting tool for your Ansible resources, it might not be that feature completed as required in some situations. If you need a more in-depth analysis you can take a look at [ansible-lint](https://github.com/ansible-community/ansible-lint).
|
|
|
|
ansible-later does **not** ensure that your role will work as expected. For Deployment test you can use other tools
|
|
like [molecule](https://github.com/ansible/molecule).
|