State management in GCP - Step-by-Step Execution

Process Flow - State management

Start Infrastructure Deployment

↓

Check Current State

↓

Compare Desired vs Current

↓

No Changes

↓

End Process

↓

Update State Storage

↓

End Process

This flow shows how GCP manages infrastructure state by checking current state, comparing with desired, applying changes if needed, and updating the stored state.

Execution Sample

GCP

terraform init
terraform plan
terraform apply

These commands initialize, plan, and apply infrastructure changes while managing state.

Process Table

Step	Action	State Checked	Changes Detected	Result
1	terraform init	No state yet	N/A	Backend configured, ready
2	terraform plan	Current state read	Yes	Shows changes to apply
3	terraform apply	Current state read	Yes	Applies changes
4	Update state storage	State updated	N/A	State saved for next run
5	terraform plan (next run)	Updated state read	No	No changes needed

💡 No changes detected after state update, deployment is stable

Status Tracker

Variable	Start	After Init	After Plan	After Apply	Final
State Storage	Empty	Configured backend	Read current state	Updated with changes	Saved updated state

Key Moments - 2 Insights

Why does terraform plan show changes before apply?

Because terraform compares the desired configuration with the current state (see execution_table step 2) and detects differences to apply.

What happens if state storage is lost?

Terraform cannot track existing resources properly, leading to potential re-creation or errors. State storage is critical (see variable_tracker).

Visual Quiz - 3 Questions

Look at the execution_table, what is the state storage status after 'terraform apply'?

A Configured backend

B Empty

C Updated with changes

D No state

💡 Hint

Check the 'State Checked' and 'Result' columns at step 4 in execution_table

At which step does terraform detect no changes needed?

A Step 2

B Step 5

C Step 3

D Step 1

💡 Hint

Look for 'No changes needed' in the 'Result' column in execution_table

If the state storage was lost after apply, what would happen on next plan?

A Terraform would re-create all resources

B Terraform would fail to run

C Terraform would detect no changes

D Terraform would skip plan

💡 Hint

Refer to key_moments about importance of state storage

Concept Snapshot

State management in GCP infrastructure tools like Terraform:
- Stores current resource info in state files
- Compares desired config with stored state
- Plans changes before applying
- Updates state after apply
- Critical to keep state safe and consistent

Full Transcript

State management in cloud infrastructure means keeping track of what resources exist and their settings. Tools like Terraform use a state file to remember current resources. When you run 'terraform plan', it reads this state and compares it to your desired setup. If differences exist, it shows what will change. Then 'terraform apply' makes those changes and updates the state file. This process ensures your cloud matches your configuration. Losing the state file can cause problems because the tool forgets what it created. So managing state carefully is key to smooth cloud deployments.