Why Arguments and expressions in Terraform? - Purpose & Use Cases

The Big Idea

What if you could change dozens of cloud settings by editing just one line of code?

The Scenario

Imagine you need to set up many cloud resources, each with slightly different settings. You write each resource's details by hand, typing every value manually.

The Problem

This manual way is slow and tiring. If you want to change a setting, you must find and edit every place it appears. Mistakes happen easily, and fixing them takes a lot of time.

The Solution

Arguments and expressions let you write flexible, reusable code. You can use variables and calculations to set values automatically, so you only change one place to update many resources.

Before vs After

✗ Before

resource "aws_instance" "example1" {
  instance_type = "t2.micro"
  ami           = "ami-123456"
}

resource "aws_instance" "example2" {
  instance_type = "t2.micro"
  ami           = "ami-654321"
}

✓ After

variable "instance_type" {
  type    = string
  default = "t2.micro"
}

resource "aws_instance" "example1" {
  instance_type = var.instance_type
  ami           = "ami-123456"
}

resource "aws_instance" "example2" {
  instance_type = var.instance_type
  ami           = "ami-654321"
}

What It Enables

You can build cloud setups that adapt easily to changes, saving time and avoiding errors.

Real Life Example

A company launches many servers with different software versions but the same hardware type. Using arguments and expressions, they change the hardware type once, and all servers update automatically.

Key Takeaways

Manual settings are slow and error-prone.

Arguments and expressions make code flexible and reusable.

They help manage cloud resources efficiently and safely.

Practice

1. What is the purpose of arguments inside a Terraform resource block?

easy

A. To set specific details or properties for the resource

B. To run commands on the resource after creation

C. To define the cloud provider used

D. To store output values from the resource

Solution

1. Step 1: Understand resource blocks

   Resource blocks define cloud resources, and arguments inside them specify details like size or name.

2. Step 2: Identify argument role

   Arguments set the properties that Terraform uses to create or manage the resource.

3. Final Answer:

   To set specific details or properties for the resource -> Option A

4. Quick Check:

   Arguments = resource details [OK]

Hint: Arguments define resource details inside blocks [OK]

Common Mistakes:

• Confusing arguments with outputs
• Thinking arguments run commands
• Mixing provider definition with arguments

2. Which of the following is the correct syntax to assign a variable value to an argument in Terraform?

easy

A. name := var.instance_name

B. name => var.instance_name

C. name == var.instance_name

D. name = var.instance_name

Solution

1. Step 1: Recall Terraform assignment syntax

   Terraform uses single equals sign (=) to assign values to arguments.

2. Step 2: Match variable usage

   Variables are referenced with var.<variable_name> and assigned using =.

3. Final Answer:

   name = var.instance_name -> Option D

4. Quick Check:

   Assignment uses = and var. prefix [OK]

Hint: Use = to assign variables in Terraform [OK]

Common Mistakes:

• Using := or == instead of =
• Confusing arrow => with assignment
• Omitting var. prefix for variables

3. Given the Terraform expression count = var.enable ? 3 : 1 and var.enable = false, what will be the value of count?

medium

A. true

B. 3

C. 1

D. false

Solution

1. Step 1: Understand the ternary expression

   The expression uses a condition: if var.enable is true, count is 3; else count is 1.

2. Step 2: Substitute variable value

   Since var.enable is false, the expression returns the value after the colon, which is 1.

3. Final Answer:

   1 -> Option C

4. Quick Check:

   False condition returns second value [OK]

Hint: Ternary returns value after colon if condition is false [OK]

Common Mistakes:

• Choosing the first value regardless of condition
• Confusing boolean with numeric output
• Ignoring variable value in expression

4. What is wrong with this Terraform argument expression?

size = var.instance_size ? "large" : "small"

assuming var.instance_size is a string variable.

medium

A. Ternary condition requires a boolean, not a string

B. Strings cannot be used in ternary expressions

C. The quotes around "large" and "small" are invalid

D. Variable names cannot be used in expressions

Solution

1. Step 1: Check ternary condition type

   The condition before ? must be boolean (true/false), but var.instance_size is a string.

2. Step 2: Identify type mismatch error

   Using a string as condition causes an error because Terraform expects a boolean expression.

3. Final Answer:

   Ternary condition requires a boolean, not a string -> Option A

4. Quick Check:

   Condition must be boolean [OK]

Hint: Ternary condition must be true/false, not string [OK]

Common Mistakes:

• Using strings as conditions
• Misplacing quotes around values
• Assuming variables can't be in expressions

5. You want to create multiple AWS EC2 instances only if var.create_instances is true. Which expression correctly sets the count argument to 5 when true, or 0 when false?

hard

A. count = var.create_instances == 5

B. count = var.create_instances ? 5 : 0

C. count = var.create_instances && 5

D. count = var.create_instances || 0

Solution

1. Step 1: Understand conditional count setting

   We want count to be 5 if var.create_instances is true, else 0.

2. Step 2: Evaluate each option

   count = var.create_instances ? 5 : 0 uses ternary: if true, 5; else 0. Options B, C, D misuse operators or return booleans.

3. Final Answer:

   count = var.create_instances ? 5 : 0 -> Option B

4. Quick Check:

   Ternary sets count correctly [OK]

Hint: Use ternary to set count based on boolean variable [OK]

Common Mistakes:

• Using boolean expressions instead of numbers for count
• Confusing && and || operators for count
• Not using ternary for conditional count