Ansible Mastery (Senior → Principal)

Operate

• Start from ownership, blast radius, and idempotent change safety.
• Treat Ansible as an automation and operations contract, not a shell script launcher.
• Prefer readable roles, predictable inventories, and explicit change boundaries.
• Optimize for safe execution, auditability, and recovery from bad automation.

Default Standards

• Idempotency is non-negotiable.
• Inventory design must reflect ownership and environment reality.
• Roles should encode reusable operational intent, not random task piles.
• Secrets and privilege escalation require strict discipline.
• Dry runs, diff visibility, and rollback posture matter.

References