Why testing infrastructure matters in Terraform - See It in Action

Why Testing Infrastructure Matters

📖 Scenario: You are working as a cloud engineer for a small company. Your team wants to make sure that the infrastructure you create with Terraform is reliable and works as expected before using it in real projects.Testing infrastructure means checking your Terraform code to catch mistakes early. This helps avoid problems like creating wrong resources or wasting money on unused servers.

🎯 Goal: Build a simple Terraform configuration for an AWS S3 bucket and add a basic test to verify the bucket's name. This will show why testing infrastructure matters by catching errors before deployment.

📋 What You'll Learn

Create a Terraform configuration with an AWS S3 bucket named exactly 'my-test-bucket'

Add a variable to hold the bucket name

Write a Terraform output to show the bucket name

Add a simple test using locals and a null_resource to check the bucket name

💡 Why This Matters

🌍 Real World

In real projects, testing infrastructure code prevents mistakes that can cause downtime or extra costs. It helps teams deliver reliable cloud setups.

💼 Career

Cloud engineers and DevOps professionals use infrastructure testing to ensure their Terraform code works correctly before applying changes to live environments.

1

Create the initial Terraform configuration with an AWS S3 bucket

Write a Terraform resource block named aws_s3_bucket with the resource name my_bucket. Set the bucket name to the exact string "my-test-bucket".

Terraform

# Your code here

Hint

Use the resource keyword, specify aws_s3_bucket, and set bucket to "my-test-bucket".

2

Add a variable to hold the bucket name

Create a Terraform variable named bucket_name with the default value "my-test-bucket". Then update the aws_s3_bucket.my_bucket resource to use this variable for the bucket name.

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = var.bucket_name
}

# Your code here

Hint

Define a variable block with default = "my-test-bucket" and use var.bucket_name in the resource.

3

Add an output to show the bucket name

Create a Terraform output named bucket_name_output that outputs the value of aws_s3_bucket.my_bucket.bucket.

Terraform

variable "bucket_name" {
  type    = string
  default = "my-test-bucket"
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = var.bucket_name
}

# Your code here

Hint

Use an output block with the value set to the bucket's name attribute.

4

Add a simple test to validate the bucket name

Add a Terraform locals block with a variable expected_bucket_name set to "my-test-bucket". Then add a terraform validate style check by creating a null_resource named test_bucket_name with a count that is 1 if aws_s3_bucket.my_bucket.bucket equals local.expected_bucket_name, otherwise 0.

Terraform

variable "bucket_name" {
  type    = string
  default = "my-test-bucket"
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = var.bucket_name
}

output "bucket_name_output" {
  value = aws_s3_bucket.my_bucket.bucket
}

# Your code here

Hint

Use a locals block for the expected name and a null_resource with a count conditional to simulate a test.

Practice

1. Why is it important to test your Terraform infrastructure before applying changes?

easy

A. To make the code run faster

B. To automatically fix bugs in your cloud provider

C. To reduce the size of your Terraform files

D. To catch errors early and avoid breaking your cloud setup

Solution

1. Step 1: Understand the purpose of testing infrastructure

   Testing helps find mistakes before they affect your live cloud environment.

2. Step 2: Identify the benefit of early error detection

   Finding errors early saves time and prevents service disruptions.

3. Final Answer:

   To catch errors early and avoid breaking your cloud setup -> Option D

4. Quick Check:

   Testing prevents errors = B [OK]

Hint: Testing finds errors before they cause problems [OK]

Common Mistakes:

• Thinking testing makes code faster
• Believing testing reduces file size
• Assuming testing fixes bugs automatically

2. Which Terraform command checks if your configuration files are syntactically valid without applying changes?

easy

A. terraform destroy

B. terraform apply

C. terraform validate

D. terraform output

Solution

1. Step 1: Identify the command for syntax checking

   Terraform validate checks the syntax and structure of configuration files.

2. Step 2: Differentiate from other commands

   Apply changes resources, destroy deletes them, output shows values; only validate checks syntax without changes.

3. Final Answer:

   terraform validate -> Option C

4. Quick Check:

   Syntax check = terraform validate [OK]

Hint: Use 'terraform validate' to check syntax only [OK]

Common Mistakes:

• Using 'terraform apply' to check syntax
• Confusing 'terraform destroy' with validation
• Thinking 'terraform output' validates files

3. Given this Terraform command sequence:

terraform validate
terraform plan
terraform apply

What is the main purpose of running terraform plan before terraform apply?

medium

A. To preview changes without applying them

B. To execute changes immediately

C. To delete existing infrastructure

D. To generate output variables

Solution

1. Step 1: Understand the role of 'terraform plan'

   This command shows what changes Terraform will make without applying them.

2. Step 2: Compare with other commands

   Apply executes changes, destroy deletes resources, output shows values; plan previews changes.

3. Final Answer:

   To preview changes without applying them -> Option A

4. Quick Check:

   Plan previews changes = A [OK]

Hint: Plan shows changes before applying [OK]

Common Mistakes:

• Thinking plan applies changes
• Confusing plan with destroy
• Believing plan generates outputs

4. You run terraform validate and get an error about a missing required argument. What should you do to fix this?

medium

A. Add the missing argument to your Terraform configuration file

B. Run terraform apply to fix the error automatically

C. Delete the Terraform configuration file

D. Ignore the error and continue

Solution

1. Step 1: Understand the error cause

   The error means your config lacks a required setting Terraform needs.

2. Step 2: Correct the configuration

   Add the missing argument to fix the syntax and meet requirements.

3. Final Answer:

   Add the missing argument to your Terraform configuration file -> Option A

4. Quick Check:

   Fix config errors by adding missing parts = C [OK]

Hint: Fix errors by completing config, not skipping steps [OK]

Common Mistakes:

• Trying to apply without fixing errors
• Deleting config files instead of fixing
• Ignoring errors and hoping for the best

5. You want to ensure your Terraform changes won't cause downtime. Which testing approach helps you achieve this before applying changes?

hard

A. Delete all resources and recreate them

B. Run terraform plan to review changes and use a staging environment

C. Skip testing and monitor after deployment

D. Directly run terraform apply on production

Solution

1. Step 1: Identify safe testing practices

   Using terraform plan previews changes; staging environment tests safely without affecting production.

2. Step 2: Avoid risky actions

   Applying directly risks downtime; skipping tests or deleting resources causes outages.

3. Final Answer:

   Run terraform plan to review changes and use a staging environment -> Option B

4. Quick Check:

   Plan + staging = safe testing [OK]

Hint: Use plan and staging to avoid downtime [OK]

Common Mistakes:

• Applying changes directly to production
• Skipping tests before deployment
• Deleting resources instead of updating