Configuration Management Cheat Sheet

Updated 2026-04-28

Next Topic: Continuous Testing Cheat Sheet

Configuration management is the systematic process of handling changes to IT systems, infrastructure, and software configurations in a controlled, consistent, and documented manner. It encompasses tracking state across resources, maintaining version control over infrastructure code, and ensuring idempotency in deployments to prevent configuration drift. Configuration management bridges the gap between initial provisioning and ongoing operational stability, enabling teams to define, deploy, and maintain desired states across development, staging, and production environments while reducing manual errors and enforcing compliance through automated, repeatable processes. In 2026, the discipline has expanded to include platform engineering patterns like Internal Developer Platforms (IDPs) and golden paths, alongside Kubernetes-native control planes like Crossplane.

What This Cheat Sheet Covers

This topic spans 19 focused tables and 166 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Core ConceptsTable 2: Configuration Management ApproachesTable 3: Configuration Management ToolsTable 4: Configuration ComponentsTable 5: State and VersioningTable 6: Secrets ManagementTable 7: Testing and ValidationTable 8: Policy and ComplianceTable 9: Configuration Drift DetectionTable 10: Environment ManagementTable 11: Infrastructure ProvisioningTable 12: Template EnginesTable 13: Change ManagementTable 14: GitOps WorkflowsTable 15: Kubernetes ConfigurationTable 16: Multi-Cloud and Hybrid ManagementTable 17: Automation and SchedulingTable 18: Observability and Monitoring IntegrationTable 19: Advanced Patterns

Table 1: Core Concepts

Concept	Example	Description
Idempotency	`ansible-playbook site.yml` (run multiple times, same result)	• Ability to apply an operation multiple times without changing the result beyond initial execution • ensures consistent configurations regardless of run frequency.
Configuration Drift	Manual server change bypasses automation; detected by comparing actual vs. desired state	• Gradual divergence of a system's active state from its intended baseline • occurs when manual changes accumulate outside the configuration management process.
Desired State Configuration	Define server should have IIS enabled; tool ensures it remains enabled	• Declarative approach where you specify what the system should look like rather than how to configure it • the system automatically maintains that state.
Infrastructure as Code (IaC)	Terraform `.tf` files or Ansible playbooks define all infrastructure in version-controlled code	Managing and provisioning infrastructure through machine-readable configuration files rather than manual processes or interactive tools.

Table 1: Core Concepts

Concept	Example	Description
Idempotency	`ansible-playbook site.yml` (run multiple times, same result)	• Ability to apply an operation multiple times without changing the result beyond initial execution • ensures consistent configurations regardless of run frequency.
Configuration Drift	Manual server change bypasses automation; detected by comparing actual vs. desired state	• Gradual divergence of a system's active state from its intended baseline • occurs when manual changes accumulate outside the configuration management process.
Desired State Configuration	Define server should have IIS enabled; tool ensures it remains enabled	• Declarative approach where you specify what the system should look like rather than how to configure it • the system automatically maintains that state.
Infrastructure as Code (IaC)	Terraform `.tf` files or Ansible playbooks define all infrastructure in version-controlled code	Managing and provisioning infrastructure through machine-readable configuration files rather than manual processes or interactive tools.