Automation — From Manual to Infrastructure as Code
Automation — From Manual to Infrastructure as Code
Managing one server manually is feasible. Managing fifty is not. This category documents the automation stack — from Ansible playbooks to Terraform infrastructure provisioning and GitOps workflows.
What this category covers
| Topic | Status |
|---|---|
| Ansible — inventory, ad-hoc, playbooks | ✅ |
| Ansible roles — nginx, mariadb, php | ✅ |
| Idempotence — changed vs ok | ✅ |
| Ansible variables and Jinja2 templates | ⏸ |
| Ansible handlers | ⏸ |
| Ansible Vault — encrypted secrets | ⏸ |
| Terraform — providers, state, modules | ⬜ |
| GitOps with ArgoCD / Flux | ⬜ |
Posts in this category cover Module 08 — Ansible, Module 13 — Terraform and Module 28 — GitOps of the roadmap.
This post is licensed under CC BY 4.0 by the author.