||1 day ago|
|.chglog||1 month ago|
|.github||5 months ago|
|ansiblelater||3 days ago|
|docker||2 weeks ago|
|docs||2 weeks ago|
|.dictionary||5 months ago|
|.drone.jsonnet||2 weeks ago|
|.drone.yml||2 weeks ago|
|.gitignore||7 months ago|
|.markdownlint.yml||1 year ago|
|.prettierignore||6 months ago|
|CONTRIBUTING.md||10 months ago|
|LICENSE||10 months ago|
|Makefile||1 week ago|
|README.md||9 months ago|
|codecov.yml||10 months ago|
|poetry.lock||1 day ago|
|pyproject.toml||1 day ago|
|renovate.json||2 weeks ago|
|setup.cfg||4 months ago|
Another best practice scanner for Ansible roles and playbooks
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.
ansible-later does not ensure that your role will work as expected. For deployment tests you can use other tools like molecule.
You can find the full documentation at https://ansible-later.geekdocs.de.
ansible-later is a fork of Will Thames ansible-review. Thanks for your work on ansible-review and ansible-lint.
This project is licensed under the MIT License - see the LICENSE file for details.