Writing less bad Ansible code (GER)
Ansible enjoys great popularity not least because of its very simple syntax. Thanks to low entry barriers, initial successes can be achieved in a short time. Unfortunately, the Internet is also full of bad examples – and so beginners can quickly acquire a bad development style. This presentation lists the worst crimes and shows how to avoid them.
Agenda:
- Motivation
- Characteristics of good code
- Common entry errors
- Structure
- Syntax / Semantics
- Variables
- Worst of Ansible
- Particularly creative errors
- Do’s and Don’ts
- Debugging
- Tools for better development
- yamllint
- ansible-lint
- ansible-test
- molecule
- assert / testinfra
Christian Stankowic is Technical Leader at SVA System Vertrieb Alexander GmbH, where he focuses on enterprise Linux, automation and DevOps. He likes to develop open-source tools for the grey boxes in his spare time, which help you solve problems that you wouldn’t have had without them.