Why workspaces separate environments in Terraform - See It in Action

Why Workspaces Separate Environments in Terraform

📖 Scenario: You are managing cloud infrastructure using Terraform. You want to keep your development and production environments separate to avoid accidental changes and to manage resources safely.

🎯 Goal: Build a Terraform configuration that uses workspaces to separate dev and prod environments, showing how to create and switch workspaces and use workspace-specific variables.

📋 What You'll Learn

Create a Terraform configuration with a resource that uses workspace-specific naming

Create two workspaces named dev and prod

Use a variable that changes based on the current workspace

Show how to switch between workspaces

💡 Why This Matters

🌍 Real World

Separating environments like development, staging, and production is critical in cloud infrastructure to prevent accidental resource changes and to test safely.

💼 Career

Cloud engineers and DevOps professionals use Terraform workspaces to manage multiple environments efficiently and safely.

1

Create a Terraform configuration with a variable for environment

Create a Terraform file named main.tf with a variable called environment of type string and default value dev. Also, define a resource aws_s3_bucket named my_bucket that uses the environment variable in its bucket name as my-bucket-${environment}.

Terraform

# Define variable environment and resource aws_s3_bucket with bucket name using environment

Hint

Use variable block to define environment and use var.environment inside the resource.

2

Create Terraform workspaces for dev and prod environments

Add instructions in a comment in main.tf to create two Terraform workspaces named dev and prod using the command terraform workspace new. Also add a comment showing how to list workspaces with terraform workspace list.

Terraform

variable "environment" {
  type    = string
  default = "dev"
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-bucket-${var.environment}"
  acl    = "private"
}

# Your code here: Add comments with terraform workspace commands

Hint

Use comments starting with # to add the workspace commands.

3

Use Terraform workspace to set environment variable dynamically

Modify main.tf to remove the default value of environment variable. Instead, create a local variable called current_env that uses the Terraform workspace name with terraform.workspace. Then update the aws_s3_bucket resource to use current_env for the bucket name.

Terraform

variable "environment" {
  type = string
  # Remove default value
}

# Define local variable current_env using terraform.workspace

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-bucket-${local.current_env}"
  acl    = "private"
}

Hint

Use locals block to define current_env as terraform.workspace.

4

Switch between workspaces and apply configuration

Add comments in main.tf showing how to switch to the prod workspace using terraform workspace select prod and how to apply the configuration with terraform apply. This completes the setup to separate environments using workspaces.

Terraform

variable "environment" {
  type = string
}

locals {
  current_env = terraform.workspace
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-bucket-${local.current_env}"
  acl    = "private"
}

# Your code here: Add comments for switching workspace and applying

Hint

Use comments to show the commands for switching workspace and applying.

Practice

1. What is the main reason Terraform workspaces are used to separate environments?

easy

A. To share the same state file across all environments

B. To keep state files separate for different environments

C. To write different Terraform code for each environment

D. To deploy resources only in the default environment

Solution

1. Step 1: Understand workspace purpose

   Terraform workspaces allow managing multiple environments using the same code but separate state files.

2. Step 2: Identify how environments stay separate

   Each workspace has its own state file, so resources do not mix between environments.

3. Final Answer:

   To keep state files separate for different environments -> Option B

4. Quick Check:

   Separate state files = separate environments [OK]

Hint: Workspaces separate state files, not code [OK]

Common Mistakes:

• Thinking workspaces require different code files
• Believing all environments share one state file
• Assuming workspaces only work for default environment

2. Which command correctly creates a new Terraform workspace named staging?

easy

A. terraform new workspace staging

B. terraform create workspace staging

C. terraform workspace new staging

D. terraform workspace create staging

Solution

1. Step 1: Recall Terraform workspace creation syntax

   The correct command to create a workspace is terraform workspace new <name>.

2. Step 2: Match the command to options

   Only terraform workspace new staging matches the correct syntax exactly.

3. Final Answer:

   terraform workspace new staging -> Option C

4. Quick Check:

   Use 'terraform workspace new' to add workspaces [OK]

Hint: Remember: 'terraform workspace new' creates new workspace [OK]

Common Mistakes:

• Using 'terraform create workspace' which is invalid
• Using 'terraform new workspace' which is not a command
• Using 'terraform workspace create' which is invalid

3. Given the following commands run in order:

terraform workspace new dev
terraform workspace select dev
terraform apply
terraform workspace select default
terraform apply

What happens to the resources?

medium

A. Resources are created separately in 'dev' and 'default' environments

B. Resources from 'dev' overwrite those in 'default'

C. Only one set of resources is created in the default workspace

D. Terraform throws an error on switching workspaces

Solution

1. Step 1: Analyze workspace creation and selection

   The 'dev' workspace is created and selected, then resources are applied there.

2. Step 2: Switch to 'default' workspace and apply again

   Switching to 'default' workspace applies resources separately using its own state file.

3. Final Answer:

   Resources are created separately in 'dev' and 'default' environments -> Option A

4. Quick Check:

   Different workspaces = separate resource sets [OK]

Hint: Switching workspaces uses separate states, so resources stay separate [OK]

Common Mistakes:

• Assuming resources merge across workspaces
• Thinking switching workspaces causes errors
• Believing only one workspace can have resources

4. You run terraform workspace select prod but get an error: Workspace 'prod' does not exist. What is the best fix?

medium

A. Run terraform workspace new prod before selecting

B. Edit the Terraform code to add 'prod' workspace

C. Delete the current workspace and retry

D. Run terraform init again

Solution

1. Step 1: Understand the error meaning

   The error means the 'prod' workspace does not exist yet in Terraform.

2. Step 2: Create the missing workspace

   Use terraform workspace new prod to add it before selecting.

3. Final Answer:

   Run terraform workspace new prod before selecting -> Option A

4. Quick Check:

   Create workspace before selecting it [OK]

Hint: Create workspace first, then select it [OK]

Common Mistakes:

• Trying to select a workspace that doesn't exist
• Editing code instead of managing workspaces
• Reinitializing Terraform unnecessarily

5. You want to deploy the same Terraform configuration to dev, staging, and prod environments using workspaces. Which approach best avoids resource conflicts and keeps environments isolated?

hard

A. Deploy all environments in the default workspace with different variable files

B. Use one workspace and manually change resource names for each environment

C. Use different Terraform configuration files for each environment in one workspace

D. Create separate workspaces for each environment and deploy in each workspace

Solution

1. Step 1: Understand workspace isolation

   Each workspace has its own state file, so creating separate workspaces isolates environments safely.

2. Step 2: Compare options for managing multiple environments

   Using separate workspaces avoids manual renaming and code duplication, reducing errors.

3. Final Answer:

   Create separate workspaces for each environment and deploy in each workspace -> Option D

4. Quick Check:

   Separate workspaces = isolated environments [OK]

Hint: Use separate workspaces per environment for clean separation [OK]

Common Mistakes:

• Trying to manage all environments in one workspace
• Duplicating code instead of using workspaces
• Relying on variable files without workspace separation