Arguments and expressions in Terraform - Commands & Configuration

Introduction

Terraform uses arguments and expressions to set values and calculate results in configuration files. This helps you customize resources and reuse values without repeating yourself.

When you want to set a resource property using a fixed value like a name or size.

When you need to calculate a value based on other variables or resource attributes.

When you want to reuse a value multiple times without typing it again.

When you want to use conditional logic to choose between values.

When you want to combine strings or lists to create complex configurations.

Config File - main.tf

main.tf

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

resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = var.environment == "prod" ? "t3.large" : "t3.micro"
  tags = {
    Name = "example-${var.environment}"
  }
}

This file defines a variable environment with a default value.

The aws_instance resource uses an expression to choose the instance type based on the environment.

The tag Name uses string interpolation to include the environment name.

Commands

Initializes the Terraform working directory and downloads necessary provider plugins.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding latest version of hashicorp/aws...

- Installing hashicorp/aws v4.0.0...

- Installed hashicorp/aws v4.0.0 (signed by HashiCorp)



Terraform has been successfully initialized!

Shows the planned actions Terraform will take based on the configuration and expressions.

Terminal

terraform plan

Expected Output

An execution plan has been generated and is shown below.

Resource actions are indicated with the following symbols:

  + create



Terraform will perform the following actions:



  # aws_instance.example will be created

  + resource "aws_instance" "example" {

      + ami           = "ami-0c55b159cbfafe1f0"

      + instance_type = "t3.micro"

      + tags          = {

          + "Name" = "example-dev"

        }

    }



Plan: 1 to add, 0 to change, 0 to destroy.

Applies the planned changes to create the resource using the arguments and expressions defined.

Terminal

terraform apply -auto-approve

Expected Output

aws_instance.example: Creating...

aws_instance.example: Still creating... [10s elapsed]

aws_instance.example: Creation complete after 15s [id=i-0abcd1234efgh5678]



Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

→

-auto-approve - Skips interactive approval to apply changes immediately

Shows any outputs defined in the configuration (none in this example, so empty).

Terminal

terraform output

Expected Output

No output (command runs silently)

Key Concept

If you remember nothing else from this pattern, remember: arguments set values and expressions calculate or choose values dynamically in Terraform configurations.

Common Mistakes

Using quotes around variables like "${var.environment}" inside expressions unnecessarily.

Terraform 0.12+ supports direct expressions without quotes, so quotes can cause errors or unexpected strings.

Use expressions directly like var.environment without extra quotes.

Trying to use expressions outside of allowed places like resource blocks or variables.

Expressions must be inside argument values; placing them incorrectly causes syntax errors.

Always put expressions as values for arguments or variables.

Not initializing Terraform before planning or applying.

Without initialization, Terraform cannot download providers and will fail.

Run terraform init first to set up the working directory.

Summary

Use arguments to assign fixed or calculated values to resource properties.

Use expressions to add logic like conditionals and string interpolation.

Run terraform init to prepare, terraform plan to preview, and terraform apply to create resources.

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