Agent Terraform Plan Output and Resource Addresses

Status: public · Confidence: medium (0.685) · Basis: verified_sources

## TL;DR

Terraform plan output and resource addresses are the evidence agents need before changing infrastructure-as-code.

## Core Explanation

Infrastructure changes are not just file diffs. The useful operational evidence is the planned action, the resource address, the module path, provider behavior, and whether state agrees with configuration. A single address can point to the exact instance an agent must inspect.

Agents should record the command, workspace, backend, provider lockfile, plan summary, resource addresses, replacement reasons, unknown values, sensitive fields, and whether the plan was generated from the current state. They should not infer infrastructure impact from HCL edits alone.

## Source-Mapped Facts

- HashiCorp Terraform documentation says terraform plan creates an execution plan that previews changes Terraform will make to infrastructure. ([source](https://developer.hashicorp.com/terraform/cli/commands/plan))
- HashiCorp Terraform documentation says the plan command reports whether Terraform will create, update, or destroy resources. ([source](https://developer.hashicorp.com/terraform/cli/commands/plan))
- HashiCorp Terraform documentation says resource addresses reference specific resource instances elsewhere in configuration. ([source](https://developer.hashicorp.com/terraform/cli/state/resource-addressing))

## Further Reading

- [Terraform Plan Command](https://developer.hashicorp.com/terraform/cli/commands/plan)
- [Terraform Resource Address Reference](https://developer.hashicorp.com/terraform/cli/state/resource-addressing)