Terraform.workspace interpolation - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to reference the current Terraform workspace.

Terraform

output "current_workspace" {
  value = terraform.[1]
}

Drag options to blanks, or click blank then click option'

Aconfig

Bstate

Cworkspace

Dmodule

Attempts:

3 left

💡 Hint

Common Mistakes

Using terraform.state instead of terraform.workspace

Trying terraform.module which is unrelated

Using terraform.config which does not exist

The terraform.workspace expression returns the name of the current workspace.

2fill in blank

medium

Complete the code to conditionally set a variable based on the current workspace.

Terraform

variable "env" {
  default = terraform.[1] == "prod" ? "production" : "development"
}

Drag options to blanks, or click blank then click option'

Amodule

Bworkspace

Cconfig

Dstate

Attempts:

3 left

💡 Hint

Common Mistakes

Using terraform.state which is not the workspace

Trying terraform.module which is unrelated

Using terraform.config which does not exist

Use terraform.workspace to get the current workspace and compare it.

3fill in blank

hard

Fix the error in the code to correctly output the workspace name.

Terraform

output "workspace_name" {
  value = terraform.[1]
}

Drag options to blanks, or click blank then click option'

Aworkspace()

Bworkspace_name()

Cworkspace_name

Dworkspace

Attempts:

3 left

💡 Hint

Common Mistakes

Adding parentheses to terraform.workspace making it a function call

Using incorrect property names like workspace_name

terraform.workspace is a property, not a function, so no parentheses are needed.

4fill in blank

hard

Fill both blanks to create a resource name that includes the current workspace.

Terraform

resource "aws_s3_bucket" "example" {
  bucket = "my-app-$[1]-$[2]"
  acl    = "private"
}

Drag options to blanks, or click blank then click option'

Aterraform.workspace

Bvar.env

Cterraform.state

Dlocal.name

Attempts:

3 left

💡 Hint

Common Mistakes

Using terraform.state which is not the workspace

Using local.name which is unrelated

Mixing up the order of workspace and env

The bucket name uses terraform.workspace and a variable var.env to include environment details.

5fill in blank

hard

Fill all three blanks to create a tag map including the workspace and environment.

Terraform

tags = {
  Name        = "app-$[1]"
  Environment = "$[2]"
  Workspace   = terraform.[3]
}

Drag options to blanks, or click blank then click option'

Avar.env

Bproduction

Cworkspace

Dlocal.env

Attempts:

3 left

💡 Hint

Common Mistakes

Using local.env instead of var.env

Using terraform.state instead of terraform.workspace

Putting quotes around terraform.workspace

The tag Name uses var.env, Environment is set to a string, and Workspace uses terraform.workspace.

Practice

1. What does terraform.workspace return when used inside a Terraform configuration?

easy

A. The name of the current workspace as a string

B. The current Terraform version

C. The list of all workspaces

D. The current directory path

Solution

1. Step 1: Understand the purpose of terraform.workspace

   terraform.workspace is a built-in Terraform variable that returns the name of the workspace currently in use.

2. Step 2: Identify what terraform.workspace returns

   It returns a string representing the workspace name, which helps differentiate environments.

3. Final Answer:

   The name of the current workspace as a string -> Option A

4. Quick Check:

   terraform.workspace = current workspace name [OK]

Hint: Remember: terraform.workspace always gives current workspace name [OK]

Common Mistakes:

• Thinking it returns Terraform version
• Confusing it with list of all workspaces
• Assuming it returns file paths

2. Which of the following is the correct syntax to use terraform.workspace inside a resource name in Terraform?

easy

A. name = myapp.${terraform.workspace}

B. name = "myapp-${terraform.workspace}"

C. name = 'myapp-terraform.workspace'

D. name = "myapp.terraform.workspace"

Solution

1. Step 1: Understand string interpolation syntax in Terraform

   Terraform uses ${} inside double quotes to insert variable values into strings.

2. Step 2: Identify correct usage of terraform.workspace

   The correct syntax is "myapp-${terraform.workspace}" to append the workspace name.

3. Final Answer:

   name = "myapp-${terraform.workspace}" -> Option B

4. Quick Check:

   Use ${} inside double quotes for interpolation [OK]

Hint: Use ${terraform.workspace} inside double quotes for interpolation [OK]

Common Mistakes:

• Using single quotes which disable interpolation
• Missing ${} around terraform.workspace
• Using dot notation without quotes

3. Given the Terraform code snippet:

output "env_name" {
  value = "Current workspace is: ${terraform.workspace}"
}

If the active workspace is staging, what will be the output value?

medium

A. An error occurs because output cannot use terraform.workspace

B. "Current workspace is: default"

C. "Current workspace is: production"

D. "Current workspace is: staging"

Solution

1. Step 1: Understand output interpolation with terraform.workspace

   The output value uses string interpolation to insert the current workspace name.

2. Step 2: Substitute the active workspace name

   Since the active workspace is staging, the output string becomes "Current workspace is: staging".

3. Final Answer:

   "Current workspace is: staging" -> Option D

4. Quick Check:

   Output string includes current workspace name [OK]

Hint: Replace ${terraform.workspace} with active workspace name [OK]

Common Mistakes:

• Assuming default workspace always
• Thinking terraform.workspace cannot be used in outputs
• Confusing workspace names

4. You wrote this Terraform resource name:

resource "aws_s3_bucket" "example" {
  bucket = 'mybucket-${terraform.workspace}'
}

But when you run Terraform, you get an error: Invalid reference. What is the likely cause?

medium

A. terraform.workspace is not available in resource blocks

B. terraform.workspace must be assigned to a variable first

C. You used single quotes instead of double quotes around the bucket name

D. You forgot to initialize Terraform workspaces

Solution

1. Step 1: Check string interpolation rules in Terraform

   Terraform requires double quotes for string interpolation; single quotes treat content as literal.

2. Step 2: Identify the error cause

   If single quotes were used, ${terraform.workspace} is not evaluated, causing an invalid reference error.

3. Final Answer:

   You used single quotes instead of double quotes around the bucket name -> Option C

4. Quick Check:

   Use double quotes for interpolation [OK]

Hint: Always use double quotes for strings with ${} interpolation [OK]

Common Mistakes:

• Using single quotes disables interpolation
• Assuming terraform.workspace needs variable assignment
• Not initializing workspaces but error is different

5. You want to create two S3 buckets using the same Terraform code but different names per workspace. You write:

resource "aws_s3_bucket" "bucket1" {
  bucket = "app-${terraform.workspace}"
}

resource "aws_s3_bucket" "bucket2" {
  bucket = "app-${terraform.workspace}"
}

What problem will occur when you apply this configuration in the dev workspace?

hard

A. Terraform will create two buckets with the same name, causing a conflict

B. Terraform will create only one bucket named "app-dev"

C. Terraform will fail because terraform.workspace cannot be used twice

D. Terraform will create buckets with different names automatically

Solution

1. Step 1: Analyze bucket names generated

   Both resources use the same bucket name pattern: "app-${terraform.workspace}". In the dev workspace, both names become "app-dev".

2. Step 2: Understand AWS S3 bucket naming constraints

   S3 bucket names must be unique globally. Creating two buckets with the same name causes a conflict error.

3. Final Answer:

   Terraform will create two buckets with the same name, causing a conflict -> Option A

4. Quick Check:

   Duplicate resource names cause conflicts [OK]

Hint: Ensure unique names per resource even with terraform.workspace [OK]

Common Mistakes:

• Assuming terraform.workspace makes names unique per resource
• Thinking Terraform merges resources automatically
• Believing terraform.workspace cannot be used multiple times