Why Terraform show for state inspection? - Purpose & Use Cases

The Big Idea

What if you could see your entire cloud setup's details instantly, without clicking through dozens of screens?

The Scenario

Imagine you have built a complex cloud setup by manually creating resources one by one. Now, you want to check what exactly is running and how everything is connected. You open multiple cloud consoles and try to piece together the current setup.

The Problem

This manual checking is slow and confusing. You might miss some resources or get wrong details because the cloud console views are scattered. It's like trying to find all your belongings in a messy room without a list.

The Solution

Terraform show lets you quickly see the full picture of your cloud setup as Terraform knows it. It reads the saved state file and shows all resources and their details in one place, like having a neat inventory list of your room.

Before vs After

✗ Before

Go to cloud console > Search resources > Check details one by one

✓ After

terraform show terraform.tfstate

What It Enables

It makes understanding and verifying your cloud setup fast and reliable by showing the exact current state in a clear way.

Real Life Example

A developer wants to confirm if a database server was created with the right size and settings before deploying an update. Using terraform show, they instantly see all details without hunting through multiple cloud dashboards.

Key Takeaways

Manual cloud inspection is slow and error-prone.

terraform show displays the full current state from Terraform's saved file.

This helps quickly verify and understand your cloud resources in one place.

Practice

1. What is the main purpose of the terraform show command?

easy

A. To apply changes to your infrastructure

B. To display the current state of your infrastructure managed by Terraform

C. To initialize a new Terraform working directory

D. To destroy all resources managed by Terraform

Solution

1. Step 1: Understand the role of terraform show

   This command is used to display the saved state of your infrastructure, showing what Terraform currently knows about your resources.

2. Step 2: Differentiate from other commands

   Commands like terraform apply, terraform init, and terraform destroy perform actions, but terraform show only displays information.

3. Final Answer:

   To display the current state of your infrastructure managed by Terraform -> Option B

4. Quick Check:

   terraform show = display state [OK]

Hint: Remember: show means display info, not change it [OK]

Common Mistakes:

• Confusing show with apply or destroy commands
• Thinking show modifies infrastructure
• Assuming show initializes Terraform

2. Which of the following is the correct syntax to display the Terraform state in JSON format?

easy

A. terraform show -json

B. terraform show --json-output

C. terraform show json

D. terraform show -format=json

Solution

1. Step 1: Recall the correct flag for JSON output

   The official Terraform command to show state in JSON format uses the -json flag.

2. Step 2: Verify other options

   Options like --json-output, json as a subcommand, or -format=json are not valid Terraform syntax.

3. Final Answer:

   terraform show -json -> Option A

4. Quick Check:

   Use -json flag for JSON output [OK]

Hint: Use '-json' flag exactly for JSON output [OK]

Common Mistakes:

• Adding extra words like '--json-output'
• Using subcommands instead of flags
• Mixing up flag syntax

3. Given the following Terraform state snippet shown by terraform show:

resource "aws_instance" "web" {
  id = "i-1234567890abcdef0"
  ami = "ami-0abcdef1234567890"
  instance_type = "t2.micro"
}

What will terraform show -json output include for the instance type?

medium

A. "instance_type": "t2.large"

B. "instance_type": "ami-0abcdef1234567890"

C. "instance_type": null

D. "instance_type": "t2.micro"

Solution

1. Step 1: Identify the instance_type in the state snippet

   The snippet shows instance_type = "t2.micro" for the resource.

2. Step 2: Understand JSON output reflects state values

   The JSON output from terraform show -json will include the exact value stored, which is "t2.micro".

3. Final Answer:

   "instance_type": "t2.micro" -> Option D

4. Quick Check:

   State value matches JSON output [OK]

Hint: JSON output matches exact state values [OK]

Common Mistakes:

• Confusing AMI ID with instance type
• Assuming default or null values
• Mixing resource attributes

4. You run terraform show -json but get an error: error: no state file found. What is the most likely cause?

medium

A. Terraform is not installed

B. The -json flag is not supported

C. Terraform state file does not exist in the current directory

D. The configuration files have syntax errors

Solution

1. Step 1: Understand the error message

   The error indicates Terraform cannot find the state file to show.

2. Step 2: Identify common reasons for missing state

   If the state file is missing from the current directory, terraform show cannot display state.

3. Final Answer:

   Terraform state file does not exist in the current directory -> Option C

4. Quick Check:

   Missing state file causes this error [OK]

Hint: Check if state file exists before show [OK]

Common Mistakes:

• Assuming -json flag is unsupported
• Thinking Terraform is not installed
• Blaming config syntax errors for state show

5. You want to programmatically extract the IDs of all AWS instances from your Terraform state. Which command and option combination is best suited for this task?

hard

A. terraform show -json | jq '.values.root_module.resources[] | select(.type=="aws_instance") | .values.id'

B. terraform show | grep aws_instance | awk '{print $2}'

C. terraform state list aws_instance

D. terraform output aws_instance_ids

Solution

1. Step 1: Understand the need for programmatic extraction

   You want to get instance IDs from the state in a machine-readable way.

2. Step 2: Evaluate command options

   terraform show -json outputs JSON, which can be filtered with jq to select AWS instances and extract their IDs. Other options either do not output JSON or do not extract IDs directly.

3. Final Answer:

   terraform show -json | jq '.values.root_module.resources[] | select(.type=="aws_instance") | .values.id' -> Option A

4. Quick Check:

   Use JSON output with jq for precise extraction [OK]

Hint: Use -json with jq to filter state data easily [OK]

Common Mistakes:

• Using grep/awk on human-readable output (fragile)
• Using terraform state list which lists names, not IDs
• Assuming terraform output has instance IDs without explicit output