Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
Terraform
Defines source-backed infrastructure as code planning and review, evidence handling, and action boundaries.
Read the fileOverview
Terraform overview
Use this bundle to structure infrastructure as code planning and review while keeping official-source context separate from account, organization, project, document, or environment evidence.
Read the fileWorkflow
Terraform source-backed triage
1. State the requested decision or deliverable. 2. Inventory evidence: Terraform and provider versions, configuration, modules, variables, and outputs, backend, workspace, state, and lock.
Read the fileTemplate
Terraform plan and change brief
Review-ready brief for infrastructure as code planning and review, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Terraform
- Teams working in Cloud infrastructure, Software
When to use it
- A proposed Terraform configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Prepare a terraform plan and change brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce review-ready decisions with explicit verification and approval boundaries.
What it helps produce
- Terraform plan and change brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Terraform and produce Terraform plan and change brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with developer.hashicorp.com — Terraform / Docs, then confirm that the reference is current and applicable. Inspect Terraform before drafting.
Context path: bundles/tools/terraform
What the bundle includes
Tools
- Terraform
Frameworks
- source-evidence matrix
- infrastructure-as-code-planning-and-review evidence matrix
- qualified-review gate
Evaluations
- Terraform source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Use official Terraform sources for general context; local infrastructure as code planning and review, configuration, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for Terraform and provider versions, configuration, modules, variables, and outputs, backend, workspace, state, and lock evidence, provider schemas and credentials boundaries, plan file, refresh behavior, and proposed actions, policy, cost, dependency, and drift evidence, and apply, rollback, and approval controls.
- Do not infer configuration, provider schema, state, workspace, plan actions, drift, credentials, infrastructure state.
Safety notes
- Minimize personal, customer, employee, financial, credential, and other sensitive data.
- Require explicit confirmation before initializing untrusted code, changing state or backends, applying plans, replacing or destroying resources, or exposing credentials.
- Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.