Skip to content
Testaroo
json4.3 KB

Terraform Plan JSON

A Terraform plan JSON document with create, update and delete changes, after_unknown markers, sensitivity annotations, and a configuration section. This is the artifact policy engines read before anything runs, which is why it sits with pipeline definitions rather than with run reports.

Preview, first 50 linesjson
{
  "format_version": "1.2",
  "terraform_version": "1.9.5",
  "planned_values": {
    "root_module": {
      "resources": [
        {
          "address": "examplecloud_network.main",
          "mode": "managed",
          "type": "examplecloud_network",
          "name": "main",
          "provider_name": "registry.example.invalid/example-org/examplecloud",
          "schema_version": 1,
          "values": {
            "name": "novus-staging-net",
            "cidr_block": "10.20.0.0/16",
            "tags": {
              "environment": "staging",
              "managed_by": "terraform"
            }
          },
          "sensitive_values": {
            "tags": {}
          }
        },
        {
          "address": "examplecloud_subnet.app[\"app-a\"]",
          "mode": "managed",
          "type": "examplecloud_subnet",
          "name": "app",
          "index": "app-a",
          "provider_name": "registry.example.invalid/example-org/examplecloud",
          "schema_version": 1,
          "values": {
            "name": "app-a",
            "cidr_block": "10.20.1.0/24",
            "zone": "a",
            "public": false
          },
          "sensitive_values": {}
        }
      ]
    }
  },
  "resource_changes": [
    {
      "address": "examplecloud_network.main",
      "mode": "managed",
      "type": "examplecloud_network",
      "name": "main",
… 178 lines total: download for the full file.

Specifications

Format Version
1.2
Terraform Version
1.9.5
Resource Changes
4
Action Kinds
create, update, delete
Has Unknown Values
true
Output Changes
1
Errored
false
Boundary
proposed change, not a run record

Testing contract

Reference control
Scenario
Run a policy check over Terraform plan JSON and classify the proposed actions
Expected result
Four resource changes are found (two creates, one update and one delete), and the delete of examplecloud_bucket.legacy is surfaced as the destructive action

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“Terraform Plan JSON” is a deterministic Testaroo fixture for Schema validation, JSON parsing, Config testing. JSON Schema documents describing a data shape, for testing validators and schema-aware tooling.

Documented properties for this file: JSON · 4,378 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Pipeline and infrastructure fixtures are inert configuration: steps reference fictional images and scripts, and nothing here executes. Run your linter, schema validator, migrator, or policy engine against them, and expect the deprecated-syntax and intentionally invalid variants to be rejected.

Code examples

import json

with open("terraform-plan.json") as f:
    data = json.load(f)
print(type(data), len(data))

Generated by generation/pipelines.py. Free for any use, no attribution required, license.