Object type definition in Terraform - Step-by-Step Execution

Process Flow - Object type definition

Start: Define object type

↓

Specify attribute names and types

↓

Use object type in variable or output

↓

Assign values matching the object structure

↓

Terraform validates types

↓

Apply configuration or error

↓

End

Define an object type by listing attribute names and their types, then use it to enforce structured data in variables or outputs.

Execution Sample

Terraform

variable "server" {
  type = object({
    name = string
    ip   = string
    port = number
  })
  default = {
    name = "web01"
    ip   = "10.0.0.1"
    port = 80
  }
}

Defines a variable 'server' with an object type having name, ip, and port attributes, then assigns default values.

Process Table

Step	Action	Attribute Checked	Expected Type	Value Provided	Validation Result
1	Start variable definition	-	-	-	Waiting for attributes
2	Define attribute 'name'	name	string	-	Defined
3	Define attribute 'ip'	ip	string	-	Defined
4	Define attribute 'port'	port	number	-	Defined
5	Assign default value for 'name'	name	string	"web01"	Valid
6	Assign default value for 'ip'	ip	string	"10.0.0.1"	Valid
7	Assign default value for 'port'	port	number	80	Valid
8	Terraform validates entire object	all	object	{name="web01", ip="10.0.0.1", port=80}	Valid
9	Variable ready for use	-	-	-	Success

💡 All attributes match their types; object variable definition is valid and ready.

Status Tracker

Variable	Start	After Step 5	After Step 6	After Step 7	Final
server.name	undefined	"web01"	"web01"	"web01"	"web01"
server.ip	undefined	undefined	"10.0.0.1"	"10.0.0.1"	"10.0.0.1"
server.port	undefined	undefined	undefined	80	80

Key Moments - 3 Insights

Why must each attribute in the object have a specified type?

Terraform checks each attribute's value against its declared type during validation (see execution_table steps 5-8). This prevents errors by ensuring data matches expected formats.

What happens if a value does not match the declared type?

Terraform will throw an error during validation (step 8), stopping the apply process until the mismatch is fixed.

Can the object have extra attributes not defined in the type?

No, Terraform only accepts attributes defined in the object type. Extra attributes cause validation errors.

Visual Quiz - 3 Questions

Look at the execution_table, what is the validation result when the 'port' attribute is assigned the value 80?

A Missing attribute error

B Valid

C Invalid type error

D Ignored

💡 Hint

Check step 7 in the execution_table where 'port' is assigned 80.

At which step does Terraform validate the entire object variable?

A Step 5

B Step 7

C Step 8

D Step 9

💡 Hint

Look for the step mentioning 'Terraform validates entire object' in the execution_table.

If the 'ip' attribute value was changed to a number, how would the validation result change at step 6?

A Invalid type error

B Still Valid

C Missing attribute error

D Ignored

💡 Hint

Refer to step 6 where 'ip' expects a string type.

Concept Snapshot

Object type definition in Terraform:
- Use object({ attr1=type1, attr2=type2, ... })
- Enforces structured data with named attributes
- Each attribute must have a declared type
- Values must match types exactly
- Terraform validates on apply
- Prevents configuration errors by type checking

Full Transcript

This visual execution shows how Terraform defines an object type variable. First, the object type is declared with attribute names and their types. Then, default values are assigned to each attribute. Terraform validates each value against its declared type step-by-step. If all values match, the object variable is ready for use. If any value mismatches, Terraform throws an error and stops. This ensures structured and type-safe configuration.