For expressions for transformation in Terraform - Mini Project: Build & Apply

Transforming a List of Server Names with Terraform For Expressions

📖 Scenario: You are managing cloud servers and have a list of server names. You want to create a new list where each server name is transformed to include a prefix that indicates the environment.

🎯 Goal: Build a Terraform configuration that uses a for expression to transform a list of server names by adding the prefix "prod-" to each name.

📋 What You'll Learn

Create a variable called server_names with the exact list: ["app1", "db1", "cache1"]

Create a variable called env_prefix with the exact value "prod-"

Use a for expression to create a local variable called prefixed_servers that adds env_prefix to each server name in server_names

Output the prefixed_servers list

💡 Why This Matters

🌍 Real World

Cloud engineers often need to manage lists of resources and apply consistent naming conventions automatically. Using for expressions in Terraform helps transform data efficiently.

💼 Career

Understanding for expressions in Terraform is essential for infrastructure as code roles, enabling automation and reducing manual errors in cloud resource management.

1

Create the server_names variable

Create a Terraform variable called server_names with the exact list ["app1", "db1", "cache1"].

Terraform

# Create the variable server_names with the list ["app1", "db1", "cache1"]
# Your code here

Hint

Use variable "server_names" block with default set to the list.

2

Create the env_prefix variable

Create a Terraform variable called env_prefix with the exact string value "prod-".

Terraform

variable "server_names" {
  type    = list(string)
  default = ["app1", "db1", "cache1"]
}

# Create the variable env_prefix with the value "prod-"
# Your code here

Hint

Use a variable block with type = string and default = "prod-".

3

Create the prefixed_servers local variable using a for expression

Create a local variable called prefixed_servers that uses a for expression to add the env_prefix to each server name in var.server_names.

Terraform

variable "server_names" {
  type    = list(string)
  default = ["app1", "db1", "cache1"]
}

variable "env_prefix" {
  type    = string
  default = "prod-"
}

# Create local.prefixed_servers using a for expression to add env_prefix to each server name
# Your code here

Hint

Use locals block with a for expression inside square brackets to transform the list.

4

Output the prefixed_servers list

Create an output called prefixed_servers that outputs the local variable prefixed_servers.

Terraform

variable "server_names" {
  type    = list(string)
  default = ["app1", "db1", "cache1"]
}

variable "env_prefix" {
  type    = string
  default = "prod-"
}

locals {
  prefixed_servers = [for name in var.server_names : "${var.env_prefix}${name}"]
}

# Create an output prefixed_servers that outputs local.prefixed_servers
# Your code here

Hint

Use an output block with value = local.prefixed_servers.

Practice

1. What does a for expression in Terraform primarily do?

easy

A. Creates a new resource in the cloud

B. Transforms each item in a list or map into a new list or map

C. Deletes resources based on a condition

D. Runs a shell command on the local machine

Solution

1. Step 1: Understand the purpose of for expressions

   For expressions in Terraform are used to transform collections like lists or maps into new collections by applying a transformation to each item.

2. Step 2: Differentiate from other Terraform actions

   Creating or deleting resources and running shell commands are not done by for expressions; they are handled by resource blocks or provisioners.

3. Final Answer:

   Transforms each item in a list or map into a new list or map -> Option B

4. Quick Check:

   For expressions = transform collections [OK]

Hint: For expressions change each item in a list/map to a new form [OK]

Common Mistakes:

• Thinking for expressions create or delete resources
• Confusing for expressions with provisioners
• Assuming for expressions run commands

2. Which of the following is the correct syntax for a simple for expression transforming a list [1, 2, 3] to their squares in Terraform?

easy

A. [for n in [1, 2, 3] : n * n]

B. [for n : n * n in [1, 2, 3]]

C. [for n in [1, 2, 3] n * n]

D. [for n in [1, 2, 3] => n * n]

Solution

1. Step 1: Recall Terraform for expression syntax

   The correct syntax is: [for <variable> in <list> : <expression>]. [for n in [1, 2, 3] : n * n] matches this exactly.

2. Step 2: Check other options for syntax errors

   [for n : n * n in [1, 2, 3]] has wrong order, [for n in [1, 2, 3] n * n] misses colon, [for n in [1, 2, 3] => n * n] uses => which is invalid in Terraform for expressions.

3. Final Answer:

   [for n in [1, 2, 3] : n * n] -> Option A

4. Quick Check:

   Correct syntax = [for var in list : expr] [OK]

Hint: Remember syntax: for var in list : expression [OK]

Common Mistakes:

• Omitting the colon ':' after the list variable
• Using arrow '=>' instead of colon
• Placing expression before 'in' keyword

3. Given the Terraform expression:

[for s in ["apple", "banana", "cherry"] : upper(s) if length(s) > 5]

What is the resulting list?

medium

A. ["banana", "cherry"]

B. ["APPLE", "BANANA", "CHERRY"]

C. ["BANANA", "CHERRY"]

D. ["APPLE"]

Solution

1. Step 1: Identify filtering condition

   The expression filters strings with length greater than 5. "banana" (6) and "cherry" (6) qualify; "apple" (5) does not.

2. Step 2: Apply transformation function

   For qualifying strings, upper(s) converts them to uppercase: "BANANA", "CHERRY".

3. Final Answer:

   ["BANANA", "CHERRY"] -> Option C

4. Quick Check:

   Filter length > 5 + uppercase = ["BANANA", "CHERRY"] [OK]

Hint: Filter first, then transform inside for expression [OK]

Common Mistakes:

• Including items that don't meet the if condition
• Not applying the upper() function
• Confusing syntax order of filter and expression

4. Identify the error in this Terraform for expression:

[for k, v in {a=1, b=2} : "${k}=${v}" if v > 1]

medium

A. Using if condition outside the for expression

B. Missing colon after the map

C. Incorrect use of string interpolation syntax

D. Using two variables without parentheses in for expression

Solution

1. Step 1: Check syntax for multiple variables in for expressions

   When using two variables (key and value) in a for expression, parentheses are required: for (k, v) in map.

2. Step 2: Identify the error in given expression

   The expression uses 'for k, v in' without parentheses, causing syntax error.

3. Final Answer:

   Using two variables without parentheses in for expression -> Option D

4. Quick Check:

   Two variables need parentheses: for (k, v) in map [OK]

Hint: Use parentheses for multiple variables in for expressions [OK]

Common Mistakes:

• Omitting parentheses around multiple variables
• Placing if condition incorrectly
• Misusing string interpolation syntax

5. You have a map of instance names to their CPU counts:

{"web"=2, "db"=4, "cache"=1}

Write a Terraform for expression that creates a list of instance names with CPU count greater than 1, all in uppercase.

hard

A. [for (name, cpu) in {"web"=2, "db"=4, "cache"=1} : upper(name) if cpu > 1]

B. [for name, cpu in {"web"=2, "db"=4, "cache"=1} : upper(name) if cpu > 1]

C. [for (name, cpu) in {"web"=2, "db"=4, "cache"=1} : name if cpu > 1]

D. [for (name, cpu) in {"web"=2, "db"=4, "cache"=1} : upper(cpu) if cpu > 1]

Solution

1. Step 1: Use parentheses for key-value iteration

   When iterating over a map with two variables, use parentheses: for (name, cpu) in map.

2. Step 2: Apply filter and transformation

   Filter with if cpu > 1 to select "web" and "db". Transform name to uppercase with upper(name).

3. Final Answer:

   [for (name, cpu) in {"web"=2, "db"=4, "cache"=1} : upper(name) if cpu > 1] -> Option A

4. Quick Check:

   Parentheses + filter + upper(name) = [for (name, cpu) in {"web"=2, "db"=4, "cache"=1} : upper(name) if cpu > 1] [OK]

Hint: Parentheses for map keys, filter with if, transform with upper() [OK]

Common Mistakes:

• Omitting parentheses for key-value pairs
• Transforming cpu instead of name
• Not filtering correctly with if condition