Ansible rewards a little discipline. These are the practices that keep it maintainable as a team and a codebase grow.
The practices
- Prefer modules over raw shell; add changed_when/creates to shell tasks
- Structure logic into roles and use group_vars/host_vars
- Encrypt secrets with Ansible Vault and keep the key out of the repo
What good looks like
A playbook that installs and enables nginx idempotently.
- hosts: web
become: true
tasks:
- name: Install nginx
ansible.builtin.package:
name: nginx
state: present
- name: Ensure nginx is running and enabled
ansible.builtin.service:
name: nginx
state: started
enabled: true
- name: Deploy site config
ansible.builtin.template:
src: site.conf.j2
dest: /etc/nginx/conf.d/site.conf
notify: reload nginx
handlers:
- name: reload nginx
ansible.builtin.service: { name: nginx, state: reloaded }Anti-patterns to retire
- Non-idempotent shell/command tasks that run every time regardless of state
- Secrets in plaintext instead of Ansible Vault
- Giant single playbooks instead of reusable roles
Want senior help putting Ansible to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.