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.

Practice

1. Which meta-argument in Terraform allows you to create multiple instances of a resource easily using an integer?

easy

A. count

B. depends_on

C. lifecycle

D. for_each

Solution

1. Step 1: Understand the purpose of count

   The count meta-argument lets you specify how many copies of a resource to create.

2. Step 2: Compare with other meta-arguments

   depends_on manages dependencies, lifecycle controls resource behavior, and for_each creates multiple instances but with keys, not just count.

3. Final Answer:

   count -> Option A

4. Quick Check:

   Multiple instances = count [OK]

Hint: Use count to repeat resources by number [OK]

Common Mistakes:

• Confusing count with depends_on
• Thinking lifecycle creates multiple resources
• Mixing count and for_each without understanding difference

2. Which of the following is the correct syntax to use the depends_on meta-argument in a resource block?

easy

A. depends_on = ["aws_instance.example"]

B. depends_on = aws_instance.example

C. depends_on = [aws_instance.example]

D. depends_on = [aws_instance.example.id]

Solution

1. Step 1: Recall depends_on syntax

   depends_on expects a list of resource references without quotes.

2. Step 2: Analyze options

   depends_on = [aws_instance.example] uses a list with resource reference correctly. depends_on = aws_instance.example misses list brackets. depends_on = ["aws_instance.example"] uses quotes making it a string, not a reference. depends_on = [aws_instance.example.id] uses an attribute which is invalid here.

3. Final Answer:

   depends_on = [aws_instance.example] -> Option C

4. Quick Check:

   List of resource references = depends_on = [aws_instance.example] [OK]

Hint: Always use square brackets with resource references for depends_on [OK]

Common Mistakes:

• Omitting brackets for depends_on list
• Using quotes around resource names
• Referencing resource attributes instead of resource itself

3. Given the following Terraform snippet:

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

What will be the number of instances created and their resource addresses?

medium

A. 1 instance: aws_instance.example

B. 3 instances: aws_instance.example[0], aws_instance.example[1], aws_instance.example[2]

C. 3 instances: aws_instance.example.0, aws_instance.example.1, aws_instance.example.2

D. Error due to missing for_each

Solution

1. Step 1: Understand count behavior

   count = 3 creates three instances indexed from 0 to 2.

2. Step 2: Identify resource addresses format

   Terraform uses square brackets for indexed resources, so addresses are aws_instance.example[0], aws_instance.example[1], and aws_instance.example[2].

3. Final Answer:

   3 instances: aws_instance.example[0], aws_instance.example[1], aws_instance.example[2] -> Option B

4. Quick Check:

   Count creates indexed instances [OK]

Hint: Count creates indexed resources with square brackets [OK]

Common Mistakes:

• Thinking only one instance is created
• Using dot notation instead of brackets for indexes
• Confusing count with for_each syntax

4. You wrote this Terraform resource:

resource "aws_s3_bucket" "example" {
  for_each = ["a", "b"]
  bucket = each.value
}

What is the error in this configuration?

medium

A. Missing count argument

B. each.value is invalid inside resource blocks

C. bucket attribute cannot use each.value

D. for_each must be a map or set, not a list

Solution

1. Step 1: Check for_each type requirements

   for_each requires a map or set of strings, not a list.

2. Step 2: Analyze provided value

   The value is a list ["a", "b"], which is invalid for for_each. It should be a set or map.

3. Final Answer:

   for_each must be a map or set, not a list -> Option D

4. Quick Check:

   for_each needs map/set, not list [OK]

Hint: Use map or set for for_each, not list [OK]

Common Mistakes:

• Using list instead of set/map for for_each
• Misunderstanding each.value usage
• Confusing count and for_each requirements

5. You want to create multiple AWS EC2 instances with different names and ensure one instance is always created before the others. Which meta-arguments combination should you use?

hard

A. Use for_each with a map of names and depends_on to order creation

B. Use count with a number and lifecycle to order creation

C. Use depends_on only, no count or for_each

D. Use lifecycle with create_before_destroy only

Solution

1. Step 1: Choose meta-argument for multiple named instances

   for_each with a map lets you create instances with specific names as keys.

2. Step 2: Ensure creation order

   depends_on lets you specify that one resource must be created before others.

3. Final Answer:

   Use for_each with a map of names and depends_on to order creation -> Option A

4. Quick Check:

   Multiple named + order = for_each + depends_on [OK]

Hint: Combine for_each and depends_on for named ordered resources [OK]

Common Mistakes:

• Using count without names for multiple instances
• Relying on lifecycle for creation order
• Ignoring depends_on for resource dependencies