Null values handling in Terraform - Step-by-Step Execution

Process Flow - Null values handling

Start

↓

Check variable value

↓

Use default or skip

↓

Apply fallback

↓

Use given value

↓

Resource or output uses value

↓

End

This flow shows how Terraform checks if a variable is null, then uses a default or fallback value if it is, otherwise it uses the given value.

Execution Sample

Terraform

variable "example" {
  type    = string
  default = null
}

output "result" {
  value = coalesce(var.example, "default_value")
}

This Terraform code defines a variable that can be null and outputs either its value or a default string if null.

Process Table

Step	Variable 'example'	Condition	Action	Output 'result'
1	null (default)	Is var.example null? Yes	Use fallback 'default_value'	"default_value"
2	set to 'hello'	Is var.example null? No	Use var.example value	"hello"
3	set to '' (empty string)	Is var.example null? No	Use var.example value	"" (empty string)
4	unset (no value)	Is var.example null? Yes	Use fallback 'default_value'	"default_value"
5	End	-	-	-

💡 Execution stops after output value is determined based on null check and fallback.

Status Tracker

Variable 'example'	Start (default null)	After 1 (null)	After 2 ('hello')	After 3 (empty string)	After 4 (unset)	Final
example	null	null	"hello"	""	null	varies per step

Key Moments - 3 Insights

Why does an empty string ('') not trigger the fallback value?

Because Terraform treats empty string as a valid non-null value, so the condition 'is null?' is false and the actual value is used (see execution_table row 3).

What happens if the variable is not set at all?

Since default=null is provided, Terraform treats an unset variable as null, so the fallback value is used (see execution_table row 4).

How does the coalesce function help with null values?

Coalesce returns the first non-null argument, so it picks the variable value if not null, otherwise the fallback (see execution_table rows 1 and 2).

Visual Quiz - 3 Questions

Look at the execution_table, what is the output 'result' when 'example' is set to 'hello'?

A "hello"

B "default_value"

C "" (empty string)

D null

💡 Hint

Check execution_table row 2 where variable 'example' is 'hello'.

At which step does Terraform use the fallback value 'default_value'?

A Step 2

B Step 1 and Step 4

C Step 3

D Step 5

💡 Hint

Look at execution_table rows where condition 'Is var.example null? Yes' is true.

If the variable 'example' is set to an empty string, what will the output be?

A "default_value"

B null

C "" (empty string)

D Error

💡 Hint

See execution_table row 3 and variable_tracker for empty string handling.

Concept Snapshot

Terraform null handling:
- Variables can be null or set.
- Use coalesce(var, fallback) to handle nulls.
- Null triggers fallback; empty string does not.
- Unset variables treated as null (with default=null).
- Outputs use first non-null value.

Full Transcript

This lesson shows how Terraform handles null values in variables. When a variable is null or unset, Terraform can use a fallback value with the coalesce function. If the variable has a real value, including an empty string, Terraform uses that value. The execution table traces different cases: default null, set to 'hello', empty string, and unset. Key moments clarify why empty strings do not trigger fallback and how unset variables behave. The visual quiz tests understanding of output values based on variable states. The concept snapshot summarizes the main points for quick reference.

Practice

1. What does a null value represent in Terraform configuration?

easy

A. A zero number

B. An empty string

C. An absence of a value or an intentional skip

D. A syntax error

Solution

1. Step 1: Understand the meaning of null in Terraform

   In Terraform, null means no value is set or the value is intentionally skipped.

2. Step 2: Differentiate null from other values

   Zero and empty string are actual values, while null means absence of any value.

3. Final Answer:

   An absence of a value or an intentional skip -> Option C

4. Quick Check:

   Null means no value set = B [OK]

Hint: Null means no value, not zero or empty string [OK]

Common Mistakes:

• Confusing null with zero
• Thinking null is an empty string
• Assuming null causes syntax error

2. Which of the following is the correct way to assign a null value to a variable in Terraform?

easy

A. variable "example" { default = null }

B. variable "example" { default = "null" }

C. variable "example" { default = '' }

D. variable "example" { default = 0 }

Solution

1. Step 1: Review Terraform syntax for null assignment

   In Terraform, null is a keyword without quotes to represent no value.

2. Step 2: Identify incorrect options

   variable "example" { default = "null" } uses quotes making it a string, C is empty string, D is zero number.

3. Final Answer:

   variable "example" { default = null } -> Option A

4. Quick Check:

   Null keyword without quotes = A [OK]

Hint: Use null without quotes to assign null value [OK]

Common Mistakes:

• Using "null" as a string instead of null keyword
• Confusing empty string with null
• Assigning zero instead of null

3. Given this Terraform expression:

var.input != null ? var.input : "default_value"

What will be the result if var.input is null?

medium

A. null

B. "default_value"

C. var.input

D. Error: invalid expression

Solution

1. Step 1: Understand the conditional expression

   The expression checks if var.input is not null; if true, returns var.input, else returns "default_value".

2. Step 2: Apply the condition when var.input is null

   Since var.input is null, the condition is false, so the expression returns "default_value".

3. Final Answer:

   "default_value" -> Option B

4. Quick Check:

   Null input returns default = A [OK]

Hint: If input is null, conditional returns default value [OK]

Common Mistakes:

• Assuming null is returned instead of default
• Thinking expression causes error
• Confusing var.input with string "var.input"

4. Identify the error in this Terraform snippet handling null values:

output "example" {
  value = var.optional_value != null ? var.optional_value : null
}

medium

A. The output block must not use variables

B. The conditional operator syntax is incorrect

C. Using null as fallback causes output to be invalid

D. No error; this is valid Terraform code

Solution

1. Step 1: Analyze the conditional expression

   The expression returns var.optional_value if not null, else returns null.

2. Step 2: Understand output block behavior with null

   Terraform outputs can have null values; it is valid and will display as null when using terraform output.

3. Final Answer:

   No error; this is valid Terraform code -> Option D

4. Quick Check:

   Outputs can accept null = D [OK]

Hint: Outputs can safely return null values [OK]

Common Mistakes:

• Believing outputs cannot accept null values
• Misreading the conditional syntax as incorrect
• Thinking variables cannot be used in output blocks

5. You want to create a resource only if a variable enable_feature is not null and true. Which Terraform expression correctly handles null values to achieve this?

hard

A. count = var.enable_feature != null && var.enable_feature == true ? 1 : 0

B. count = var.enable_feature != false ? 1 : 0

C. count = var.enable_feature ? 1 : 0

D. count = var.enable_feature != null ? 1 : 0

Solution

1. Step 1: Understand the requirement

   The resource should be created only if enable_feature is not null and true.

2. Step 2: Evaluate each option

   count = var.enable_feature != null ? 1 : 0: count = var.enable_feature != null ? 1 : 0 creates the resource if not null, regardless of true or false.
   count = var.enable_feature != false ? 1 : 0: count = var.enable_feature != false ? 1 : 0 creates for true and null (null != false).
   count = var.enable_feature ? 1 : 0: count = var.enable_feature ? 1 : 0 errors if null (invalid boolean condition).
   count = var.enable_feature != null && var.enable_feature == true ? 1 : 0: count = var.enable_feature != null && var.enable_feature == true ? 1 : 0 checks both conditions explicitly.

3. Final Answer:

   count = var.enable_feature != null && var.enable_feature == true ? 1 : 0 -> Option A

4. Quick Check:

   Check null and true explicitly = D [OK]

Hint: Check both not null and true explicitly for safe resource creation [OK]

Common Mistakes:

• Ignoring null check causing errors
• Assuming null is false automatically
• Using only one condition without null check