#367 · Developer Tool

Terraform State Viewer

Inspect a Terraform state JSON export locally and summarize modules, resources, instances, and providers. It processes the pasted configuration locally, reports useful counts, and leaves deployment or command execution to the official project tooling.

Developer Input

Terraform state JSON
Ad space

How to use this developer tool

  1. Paste the Terraform state JSON or load a local text file.
  2. Choose only the options relevant to the intended result.
  3. Select View State or press Ctrl/Cmd + Enter.
  4. Review the summary and diagnostics before copying or downloading.

What this developer tool does

Terraform State Viewer reads Terraform state JSON and produces a deterministic, copy-ready view for review. It reports counts that help confirm the expected scope before the result is used elsewhere.

The browser scans the Terraform state JSON, applies the selected transformation, and builds structured rows without uploading the source.

Official CLIs remain the final authority for rendering, validation, state changes, and deployment behavior.

Example

The sample input demonstrates the supported Terraform state JSON structure. Run it to see the exact output and populated diagnostics generated by this implementation.

{"version":4,"terraform_version":"1.9.0","serial":12,"lineage":"demo","resources":[{"mode":"managed","type":"aws_instance","name":"web","provider":"provider[\"registry.terraform.io/hashicorp/aws\"]","instances":[{"index_key":0,"attributes":{"id":"i-123","ami":"ami-123"}}]}]}

Use cases

  • Review configuration during a pull request.
  • Prepare a concise inventory for documentation.
  • Spot structural changes before running an official CLI command.
  • Export a local result for a ticket or change record.

Tips for reliable output

  • Start from a version-controlled copy.
  • Keep indentation consistent in YAML input.
  • Do not paste secrets into shared browsers or screenshots.
  • Compare downloaded output before replacing a source file.
  • Run the ecosystem CLI in CI before deployment.

Processing details

Parsing is deliberately local and bounded to patterns that can be handled reliably in a standalone browser page. The output data can also be downloaded as CSV or JSON when structured rows are available.

This page does not execute Helm, Terraform, or Ansible and cannot resolve providers, chart dependencies, plugins, remote state, or runtime precedence beyond the visible Terraform state JSON.

Frequently asked questions

Does the Terraform State Viewer send Terraform state JSON to a server?

No. Processing runs in your browser, and the page makes no request with the pasted Terraform state JSON.

What input does the Terraform State Viewer accept?

Paste the Terraform state JSON shown in the input label. The sample demonstrates the supported structure and separators.

Will comments and quoted values be preserved?

Comments are preserved where formatting permits. Quoted scalar content is not deliberately rewritten, but review output before committing it.

How are malformed blocks reported?

The tool stops on structural errors it can detect and shows a concise message. It does not claim to replace the official CLI parser.

Can I use the output in CI?

Yes, after review. Download or copy the result, then validate it with the project-specific Helm, Terraform, or Ansible command in CI.

Result fields

FieldMeaning
SummaryCounts and action performed
InterpretationScope and review note
ExportsCopy, file, CSV, or JSON when available

DevOps and Container Tools

Browse formatters, extractors, validators, and configuration helpers for container and infrastructure workflows.

View category