Ansible configuration management coding standards
In this section, we are going to list several rules and methods to help with writing nice and clean playbooks in conformity with the Ansible norm. This is not a strict instruction to follow, but instead a representation of how Ansible developers and maintainers think it should be used. Following these norms does not just allow easier usage of playbooks, it also helps make it standard and understandable by the community members, therefore enabling better team collaboration.
Note
These standards are based on the experience of Ansible users and maintainers. Any individual user may use Ansible differently, in a way that would require a different set of rules.
Playbook and task naming
When making a playbook, using the name: field is optional. If you write a playbook with no name, it will work perfectly fine. The following is an example of a playbook that does not have a name:
---
- hosts: servers
become: yes
gather_facts: false
tasks:
- apt...
