Configuration Management Cheat Sheet

Updated 2026-04-28

Next Topic: Continuous Testing Cheat Sheet

🧠Study flashcards on this topic128 cards · spaced repetition→

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, 128 flashcards. 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

Quick IndexSubscribe to unlock

A jump-to index of every table row in this cheat sheet.

Mind MapSubscribe to unlock

An interactive map of every table and concept in this topic.

Table 1: Core Concepts

These are the foundational ideas you'll keep bumping into no matter which tool you reach for — idempotency, drift, desired state, and the various flavors of "as code." Getting comfortable with this vocabulary is what makes the rest of the cheat sheet click into place.

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.
Configuration as Code	YAML/JSON files defining system settings instead of GUI clicks	Treating configuration like software code: stored in version control, peer-reviewed, tested, and deployed through automated pipelines.
State Management	`terraform.tfstate` file tracking deployed infrastructure	• Tracking of current infrastructure configuration to compare against code and detect changes • essential for reconciling actual vs. intended state.
Version Control	Git repository storing all infrastructure code with full commit history	• Managing changes to configuration code over time • enables rollback, audit trails, and collaborative development through branching and merging.
Continuous Configuration Automation	Tool runs every 30 minutes to enforce compliance policies	• Ongoing automated enforcement of configurations • continuously monitors and corrects drift to maintain desired state without manual intervention.

Table 2: Configuration Management Approaches

Before picking a tool, you're really picking a philosophy. Do you describe the end goal and let the system figure out the steps, or spell out every command yourself? Do you patch servers in place or replace them wholesale, and does the control node push changes out or do the nodes pull them in? These paired choices shape everything that follows.

Approach	Example	Description
Declarative	Define "web server must exist with 4GB RAM" → tool determines how	• Specify what the end state should be • configuration tool determines the steps needed to achieve it • most modern tools use this approach.

The rest of this section is part of the full cheat sheet

Table 3: Configuration Management Tools

The working landscape of the field, from the household names — Ansible, Terraform, Puppet, Chef — to the cloud-native control planes and the IaC newcomers that let you write infrastructure in real programming languages. Note where each one sits on the agentless-vs-agent and declarative-vs-imperative spectrum, and watch the deprecation flags so you don't invest in something on its way out.

Tool	Example	Description
Ansible	`ansible-playbook webserver.yml -i inventory.ini`	• Agentless push-based tool using YAML playbooks • executes over SSH, uses declarative and imperative styles, highly popular for simplicity.

The rest of this section is part of the full cheat sheet

Table 4: Configuration Components

Each major tool slices its work into its own named building blocks — Ansible has playbooks and roles, Terraform has modules and providers, Puppet has manifests, Chef has cookbooks, Salt has states and pillars. Lining them up side by side reveals how much the same job (declare it, group it, reuse it, keep secrets apart) repeats under different labels.

Component	Example	Description
Playbook (Ansible)	`site.yml` defining tasks to install packages and start services	• Ordered list of plays defining configurations to apply • YAML-based, combines tasks, handlers, and variables into reusable automation.

The rest of this section is part of the full cheat sheet

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.
Configuration as Code	YAML/JSON files defining system settings instead of GUI clicks	Treating configuration like software code: stored in version control, peer-reviewed, tested, and deployed through automated pipelines.
State Management	`terraform.tfstate` file tracking deployed infrastructure	• Tracking of current infrastructure configuration to compare against code and detect changes • essential for reconciling actual vs. intended state.
Version Control	Git repository storing all infrastructure code with full commit history	• Managing changes to configuration code over time • enables rollback, audit trails, and collaborative development through branching and merging.
Continuous Configuration Automation	Tool runs every 30 minutes to enforce compliance policies	• Ongoing automated enforcement of configurations • continuously monitors and corrects drift to maintain desired state without manual intervention.

Table 2: Configuration Management Approaches

Approach	Example	Description
Declarative	Define "web server must exist with 4GB RAM" → tool determines how	• Specify what the end state should be • configuration tool determines the steps needed to achieve it • most modern tools use this approach.

Table 3: Configuration Management Tools

Tool	Example	Description
Ansible	`ansible-playbook webserver.yml -i inventory.ini`	• Agentless push-based tool using YAML playbooks • executes over SSH, uses declarative and imperative styles, highly popular for simplicity.

Table 4: Configuration Components

Component	Example	Description
Playbook (Ansible)	`site.yml` defining tasks to install packages and start services	• Ordered list of plays defining configurations to apply • YAML-based, combines tasks, handlers, and variables into reusable automation.