Configuration is the set of settings or instructions that specifies how infrastructure resources are provisioned or operated. In infrastructure as code, it becomes the source of truth for resources and their changes. section 2.3.1 section 1.4.1
Use configuration to make infrastructure changes reproducible, traceable, and safer:
- Store configuration in version control and use commit messages to explain why a change was made and how it affects related infrastructure. section 2.3.1
- Review usage and dependencies before deleting configuration for unused resources; stop a questionable resource temporarily when necessary. section 12.2.1
- Reduce variation and apply reproducibility, idempotency, composability, and evolvability principles to limit change risk. section 1.4.1
Firewall change with operational context
A configuration change allowing app-network to reach shared-services-network is paired with a commit explaining that the application uses queues. A ticket prefix such as TICKET-002 adds traceability. section 2.3.1
