Terraform show for state inspection - Commands & Configuration

Introduction

Sometimes you want to see what resources Terraform has created or plans to create without changing anything. Terraform show lets you look inside the saved state file to understand your infrastructure's current setup.

When you want to check the details of resources Terraform manages without applying changes

When you need to verify the current state of your infrastructure after deployment

When you want to debug or audit what Terraform knows about your resources

When you want to export the state information in a readable format

When you want to compare the actual deployed resources with your configuration

Commands

This command initializes the Terraform working directory, downloading necessary provider plugins and preparing the environment.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding latest version of hashicorp/aws...

- Installing hashicorp/aws v4.60.0...

- Installed hashicorp/aws v4.60.0 (signed by HashiCorp)



Terraform has been successfully initialized!

This command applies the Terraform configuration to create or update infrastructure without asking for confirmation.

Terminal

terraform apply -auto-approve

Expected Output

aws_instance.example: Creating...

aws_instance.example: Still creating... [10s elapsed]

aws_instance.example: Creation complete after 15s [id=i-0abcd1234efgh5678]



Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

→

-auto-approve - Skips interactive approval prompt

This command displays the current state of the infrastructure managed by Terraform in a human-readable format.

Terminal

terraform show

Expected Output

aws_instance.example:

  id = i-0abcd1234efgh5678

  ami = ami-0c55b159cbfafe1f0

  instance_type = t2.micro

  availability_zone = us-east-1a

  tags = {

    Name = "example-instance"

  }

Key Concept

If you remember nothing else from this pattern, remember: terraform show lets you peek inside your infrastructure's current state without making changes.

Common Mistakes

Running terraform show before terraform init

Terraform needs to initialize providers and backend before it can read the state properly, otherwise it may error or show incomplete info.

Always run terraform init first to prepare the working directory.

Expecting terraform show to modify infrastructure

terraform show only displays state information; it does not create, update, or delete resources.

Use terraform apply to make changes, terraform show only to inspect.

Summary

Run terraform init to prepare your environment.

Use terraform apply -auto-approve to deploy your infrastructure.

Use terraform show to inspect the current state of your deployed resources.

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