Config as Code

Definitions

1. Managing configuration in version-controlled code files rather than through manual UI changes or scripts. If it's not in version control, it doesn't exist (until it breaks production).

   In plain English: Storing all your system settings in files that are tracked by version control, so you can see who changed what, when, and roll back if something breaks.

2. Also called Infrastructure as Code (IaC) when applied to infrastructure. Tools like Terraform, Ansible, and Pulumi embody this principle. The key benefit: changes are reviewable, reversible, and reproducible — unlike clicking through a web console at 3 AM.

   Example: 'After the third time someone manually changed a production setting and forgot to update staging, we moved everything to config-as-code with Terraform.'

   Source: IaC relationship

Related Terms

• Docker
• Terraform
• Environment Variable
• Twelve-Factor App
• infrastructure as code
• twelve-factor app
• immutable infrastructure
• Container
• Deployment
• DSC
• Orchestration
• Rake
• Shell Script
• Supervisor
• Environment Variable
• Pre-commit Hook
• Continuous Delivery
• Continuous Deployment
• Continuous Integration
• CPU Pipeline
• Deploy Pipeline
• Deployment Slot
• Deployment Strategy
• Helm Template
• Integration
• Task Runner
• Terraform Provider
• Toolchain
• Vagrant
• Virtual Device
• Automate All the Things
• Infrastructure as Code Culture
• Ansible
• Chef