Skip to main content
RunBook Academy

TerraformI · Infrastructure as Code FoundationsProduction Terraform

Drift: The Tax of Manual Infrastructure

Foundation⏱ ~12 min

What you'll learn

  • Define configuration drift
  • Explain the cost of drift
  • Identify drift sources

Prerequisites

None — start here.

Verified against Terraform CLI 1.9.x · OpenTofu 1.7.x · HCL 2.0 · bpg/proxmox provider 0.66+ · hashicorp/local provider 2.5+ · hashicorp/null provider 3.2+ · hashicorp/random provider 3.6+ · hashicorp/http provider 3.4+ · Ubuntu 24.04 LTS · Debian 12 (Bookworm)

Not yet marked complete on this device.

Objective

Define configuration drift

What this lesson covers

  • Explain the cost of drift
  • Identify drift sources

Why this matters in production

Production Terraform operations have blast radius. Drift: The Tax of Manual Infrastructure is one of the operational controls that determines whether a change is safe to apply. Skip this lesson at the cost of not understanding a production control.

How it works

Provide an overview of the topic. This lesson covers the drift: the tax of manual infrastructure concept, the underlying mechanism, and the production implications.

Key concepts.

  • The terminology used in the topic.
  • The mechanism that determines the operational behaviour.
  • The production control that mitigates the operational risk.

Operational implications.

The drift: the tax of manual infrastructure concept affects the production change-management workflow. A change in this area has blast radius across the entire estate.

How to configure it

Apply the configuration pattern:

  1. Set up the configuration block.
  2. Validate the configuration.
  3. Run the plan.
  4. Verify the operations.
  5. Document the change.

How to inspect it

Inspection pattern:

  • Use the relevant CLI command to inspect the state.
  • Verify the configuration matches the expectation.
  • Confirm the plan is empty.

Validation

The validation pattern:

  • Confirm the configuration is valid.
  • Verify the plan is empty.
  • Confirm the operations are correct.

Production failure modes

The following failure modes are the most common in production:

  1. Misconfiguration of the relevant parameter.
  2. Drift between the configuration and the real world.
  3. Provider failure during the apply.
  4. State corruption or loss.

How to recover

The recovery procedure:

  1. Investigate the failure.
  2. Identify the cause.
  3. Apply the remediation.
  4. Verify the state.
  5. Document the incident.

The following runbooks in this course apply to this lesson:

  • terraform-runbook-investigate-state-lock
  • terraform-runbook-recover-partial-apply
  • terraform-runbook-investigate-provider-failure

What comes next

The next lesson in I-Foundations continues the exploration of Drift: The Tax of Manual Infrastructure. Follow the order to maintain the production-first narrative.

Knowledge check · 8 questions

  1. Q1. What is the primary value of Infrastructure as Code?

  2. Q2. Which statement best describes declarative infrastructure?

  3. Q3. Terraform is a configuration management tool like Ansible.

  4. Q4. Which is the most common operational risk of manual infrastructure?

  5. Q5. Which of the following are benefits of IaC? (Select all that apply.)

  6. Q6. When should Terraform NOT be used for a task?

  7. Q7. A team has 50 microservices deployed by hand. They want to use Terraform. What is the first risk to mitigate?

  8. Q8. What is the difference between provisioning and configuration?

Passing score: 75%. Answers are checked in this browser.