Terraform state pull and push - Step-by-Step Execution

Process Flow - Terraform state pull and push

Start

↓

Run 'terraform state pull'

↓

Download current state file

↓

Modify state file locally (optional)

↓

Run 'terraform state push'

↓

Upload updated state file

↓

End

This flow shows how Terraform downloads the current state, optionally modifies it locally, then uploads the updated state back.

Execution Sample

Terraform

terraform state pull > terraform.tfstate
# (edit state file locally)
terraform state push terraform.tfstate

Pulls the current Terraform state, allows local changes, then pushes the updated state back.

Process Table

Step	Command	Action	Result
1	terraform state pull > terraform.tfstate	Download state file from backend	State file saved locally
2	Local edit (optional)	Modify state file content	State file updated locally
3	terraform state push terraform.tfstate	Upload local state file to backend	Backend state updated
4	-	Verify state consistency	State matches local file

💡 State push completes, backend state matches local state file

Status Tracker

Variable	Start	After Pull	After Local Edit	After Push
state_file	empty	downloaded content	modified content	uploaded content

Key Moments - 2 Insights

Why do we need to pull the state before pushing?

Pulling ensures you have the latest state file locally to avoid overwriting changes. See execution_table step 1 and 3.

What happens if the local state file is corrupted before pushing?

Pushing a corrupted state can break your Terraform setup. Always verify local edits before push (execution_table step 2).

Visual Quiz - 3 Questions

Look at the execution table, what is the result of 'terraform state pull' at step 1?

A State file saved locally

B State file uploaded to backend

C State file deleted

D No change

💡 Hint

Check the 'Result' column in execution_table row 1

At which step does the backend state get updated?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Action' and 'Result' columns in execution_table row 3

If you skip the pull and push a local state, what risk increases?

A No risk, it's safe

B Overwriting newer backend state

C Deleting local files

D Terraform version mismatch

💡 Hint

Refer to key_moments about why pulling first is important

Concept Snapshot

terraform state pull: downloads current state file from backend
terraform state push: uploads local state file to backend
Always pull before push to avoid overwriting changes
Local edits to state file should be done carefully
Push updates backend state to match local file

Full Transcript

Terraform state pull downloads the current state file from the backend to your local machine. You can optionally edit this state file locally to fix or adjust resources. After editing, terraform state push uploads the updated state file back to the backend, replacing the previous state. This process ensures your local and backend states stay synchronized. Always pull before pushing to avoid overwriting newer changes in the backend. Be careful when editing the state file locally to prevent corruption.

Practice

1. What does the terraform state pull command do?

easy

A. Deletes the current Terraform state from the backend

B. Uploads a local state file to the remote backend

C. Initializes the Terraform working directory

D. Downloads the current Terraform state file to your local machine

Solution

1. Step 1: Understand the purpose of state pull

   The terraform state pull command fetches the current state file from the remote backend and saves it locally.

2. Step 2: Differentiate from push and other commands

   Unlike push, which uploads a local state, pull only downloads the state. It does not delete or initialize anything.

3. Final Answer:

   Downloads the current Terraform state file to your local machine -> Option D

4. Quick Check:

   Pull = Download state [OK]

Hint: Pull means download state from cloud to local [OK]

Common Mistakes:

• Confusing pull with push (upload)
• Thinking pull deletes state
• Mixing pull with terraform init

2. Which is the correct syntax to upload a local state file named my.tfstate to the remote backend?

easy

A. terraform state pull my.tfstate

B. terraform state push my.tfstate

C. terraform push state my.tfstate

D. terraform upload state my.tfstate

Solution

1. Step 1: Identify the correct command for uploading state

   The command to upload a local state file to the remote backend is terraform state push followed by the filename.

2. Step 2: Verify syntax correctness

   Options C and D use invalid command structures. terraform state pull my.tfstate is for downloading, not uploading.

3. Final Answer:

   terraform state push my.tfstate -> Option B

4. Quick Check:

   Push = upload state file [OK]

Hint: Push uploads local state; syntax: terraform state push filename [OK]

Common Mistakes:

• Using pull instead of push
• Incorrect command order
• Using terraform upload which doesn't exist

3. Given you run terraform state pull and save the output to local.tfstate, what will terraform state push local.tfstate do next?

medium

A. Initialize the Terraform backend

B. Download the remote state again and overwrite local.tfstate

C. Upload the exact state you just downloaded back to the remote backend

D. Delete the remote state file

Solution

1. Step 1: Understand the pull then push sequence

   Pull downloads the current remote state to local. Push uploads a local state file to the remote backend.

2. Step 2: Analyze the effect of pushing the pulled state

   Pushing the same file you pulled will overwrite the remote state with the same content, effectively restoring it.

3. Final Answer:

   Upload the exact state you just downloaded back to the remote backend -> Option C

4. Quick Check:

   Pull then push = download then upload same state [OK]

Hint: Push after pull uploads the same state back [OK]

Common Mistakes:

• Thinking push downloads state
• Assuming push deletes state
• Confusing push with init

4. You tried to run terraform state push without specifying a file. What error will you most likely see?

medium

A. Error: Missing required argument: filename

B. State pushed successfully

C. Error: No state file found in current directory

D. Error: Backend not initialized

Solution

1. Step 1: Check command requirements

   The terraform state push command requires a filename argument to specify which local state file to upload.

2. Step 2: Identify error when argument is missing

   Without the filename, Terraform will return an error about the missing required argument.

3. Final Answer:

   Error: Missing required argument: filename -> Option A

4. Quick Check:

   Push needs filename argument [OK]

Hint: Push command needs a file name argument [OK]

Common Mistakes:

• Running push without filename
• Expecting push to work without arguments
• Confusing missing file error with backend init error

5. You have a corrupted local state file and want to fix your remote state safely. Which sequence of commands should you use?

hard

A. Run terraform state pull to download the remote state, fix the local file, then terraform state push to upload it

B. Run terraform state push first, then terraform state pull

C. Delete the remote state manually, then run terraform init

D. Run terraform refresh to fix the state automatically

Solution

1. Step 1: Download the current remote state safely

   Use terraform state pull to get the latest remote state to your local machine.

2. Step 2: Fix the corrupted local state file

   Edit or repair the downloaded state file carefully to correct corruption.

3. Step 3: Upload the fixed state back to remote

   Use terraform state push to update the remote backend with the corrected state file.

4. Final Answer:

   Run terraform state pull to download the remote state, fix the local file, then terraform state push to upload it -> Option A

5. Quick Check:

   Pull, fix, then push = safe state repair [OK]

Hint: Pull remote state, fix locally, then push back [OK]

Common Mistakes:

• Pushing corrupted state first
• Deleting remote state manually
• Expecting terraform refresh to fix state file