Block syntax and structure in Terraform - Step-by-Step Execution

Process Flow - Block syntax and structure

Start Terraform File

↓

Read Block Type

↓

Read Block Label(s) if any

↓

Parse Block Body

↓

Store Block Configuration

↓

Repeat for Next Block or End

Terraform files are made of blocks. Each block has a type, optional labels, and a body with settings. Terraform reads each block in order and stores its configuration.

Execution Sample

Terraform

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

Defines an AWS instance resource block with type, label, and settings inside.

Process Table

Step	Action	Block Type	Labels	Body Parsed	Result
1	Start reading file	N/A	N/A	N/A	Ready to parse blocks
2	Read block type	resource	N/A	N/A	Identified resource block
3	Read block labels	resource	aws_instance, web	N/A	Labels assigned
4	Parse block body	resource	aws_instance, web	{ami = "ami-123456", instance_type = "t2.micro"}	Settings stored
5	End of block	resource	aws_instance, web	N/A	Block complete
6	Check for more blocks	N/A	N/A	N/A	No more blocks, finish parsing

💡 All blocks parsed, file reading complete

Status Tracker

Variable	Start	After Step 3	After Step 4	Final
block_type	N/A	resource	resource	resource
labels	N/A	["aws_instance", "web"]	["aws_instance", "web"]	["aws_instance", "web"]
body	N/A	N/A	{"ami": "ami-123456", "instance_type": "t2.micro"}	{"ami": "ami-123456", "instance_type": "t2.micro"}

Key Moments - 2 Insights

Why do blocks sometimes have labels and sometimes not?

Labels identify specific instances of a block type, like resource names. See step 3 in execution_table where labels are read after the block type.

What happens if the block body is empty?

Terraform stores an empty configuration for that block. The body parsing step (step 4) would parse no settings but still complete the block.

Visual Quiz - 3 Questions

Look at the execution table, what labels are assigned at step 3?

A ["web"]

B ["aws_instance", "web"]

C No labels

D ["resource"]

💡 Hint

Check the 'Labels' column in row for step 3

At which step is the block body parsed and stored?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Body Parsed' and 'Result' columns in the execution_table

If a block had no labels, which step would show empty labels?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Labels are read at step 3; check the 'Labels' column there

Concept Snapshot

Terraform blocks have this structure:
block_type "label1" "label2" {
  key = value
}

- Block type is required
- Labels are optional identifiers
- Body contains key-value settings
- Terraform reads blocks top to bottom
- Each block configures part of infrastructure

Full Transcript

Terraform files are made of blocks. Each block starts with a block type, like resource or variable. Some blocks have labels to identify them, like resource "aws_instance" "web". Inside the block is the body with settings, such as ami and instance_type. Terraform reads the file line by line, identifies the block type, then reads any labels, then parses the body. It stores this configuration to build infrastructure. This flow repeats for each block until the file ends. Understanding this structure helps you write valid Terraform code.