Meta-arguments overview in Terraform - Step-by-Step Execution

Process Flow - Meta-arguments overview

Start Resource Block

↓

Define Meta-arguments?

↓

Apply Meta-arguments

↓

Resource Creation

↓

End

Terraform resources can include special meta-arguments that control how Terraform processes them, like loops or dependencies.

Execution Sample

Terraform

resource "aws_instance" "example" {
  count = 3
  ami = "ami-123456"
  instance_type = "t2.micro"
}

Creates 3 instances using the 'count' meta-argument to repeat the resource.

Process Table

Step	Meta-argument	Value	Action	Result
1	count	3	Terraform reads 'count' meta-argument	Prepare to create 3 instances
2	ami	"ami-123456"	Set AMI for instances	AMI set for all instances
3	instance_type	"t2.micro"	Set instance type	Instance type set for all instances
4	count	3	Create instances 0,1,2	3 instances created
5	depends_on	none	No explicit dependencies	Resources created independently
6	for_each	not used	No for_each meta-argument	No iteration by keys
7	lifecycle	default	Default lifecycle applies	Resource lifecycle managed normally
8	-	-	Resource creation complete	Terraform state updated

💡 All meta-arguments processed; 3 instances created as specified by 'count'

Status Tracker

Variable	Start	After Step 1	After Step 4	Final
count	undefined	3	3	3
ami	undefined	"ami-123456"	"ami-123456"	"ami-123456"
instance_type	undefined	"t2.micro"	"t2.micro"	"t2.micro"
instances_created	0	0	3	3

Key Moments - 3 Insights

Why does Terraform create 3 instances instead of 1?

Because the 'count' meta-argument is set to 3 (see execution_table step 1), Terraform repeats the resource creation 3 times.

What happens if 'depends_on' is not specified?

Terraform assumes no explicit dependencies and creates resources independently (see execution_table step 5).

Can 'for_each' and 'count' be used together?

No, Terraform does not allow both 'count' and 'for_each' in the same resource block to avoid conflicts.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Terraform decide how many instances to create?

A Step 3

B Step 1

C Step 5

D Step 7

💡 Hint

Check the step where 'count' meta-argument is read and used.

According to variable_tracker, what is the value of 'instances_created' after step 4?

A 0

B 1

C 3

D undefined

💡 Hint

Look at the 'instances_created' row and the 'After Step 4' column.

If we add 'for_each' meta-argument alongside 'count', what will happen?

A Terraform will throw an error

B Terraform will ignore 'for_each'

C Terraform will create resources using both loops

D Terraform will ignore 'count'

💡 Hint

Recall the key moment about using 'count' and 'for_each' together.

Concept Snapshot

Meta-arguments in Terraform control resource behavior.
Common meta-arguments: count, for_each, depends_on, lifecycle.
'count' repeats resource creation N times.
'for_each' iterates over a map or set.
'depends_on' sets explicit dependencies.
Only one of 'count' or 'for_each' can be used per resource.

Full Transcript

Terraform uses meta-arguments to control how resources are created and managed. For example, 'count' tells Terraform to create multiple copies of a resource. In the example, setting count=3 creates three instances. Terraform reads these meta-arguments first, then applies the resource settings like AMI and instance type. If 'depends_on' is not set, Terraform creates resources independently. 'for_each' is another meta-argument for iteration but cannot be combined with 'count'. Understanding these meta-arguments helps manage infrastructure efficiently.