Professional review status
No professional domain review recorded
This bundle covers financial, legal, privacy, safety, security subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.
Review before reliance: An authorized product owner and domain, privacy, security, legal, financial, safety, employment, tax, healthcare, or other qualified reviewer appropriate to the data and proposed action.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
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
OpenTofu
source-backed guidance for OpenTofu.
Read the fileOverview
OpenTofu overview
source-backed guidance for OpenTofu infrastructure as code, providers, modules, state, plans, applies, workspaces, testing, state encryption, automation, migration, and governance.
Read the fileWorkflow
OpenTofu source-backed workflow
Verify-first workflow for OpenTofu infrastructure, state, and change review brief.
Read the fileTemplate
OpenTofu infrastructure, state, and change review brief
Review template for source-grounded OpenTofu work.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in OpenTofu
- Teams working in Technology, Business operations
When to use it
- A proposed OpenTofu 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
- Review product use from current official sources and inspected local evidence.
- Prepare a controlled decision without inventing account state, access, data, execution, or results.
What it helps produce
- OpenTofu infrastructure, state, and change review 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 OpenTofu and produce OpenTofu infrastructure, state, and change review brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Ground the review in this documented product scope: source-backed guidance for OpenTofu infrastructure as code, providers, modules, state, plans, applies, workspaces, testing, state encryption, automation, migration, and governance. Begin with opentofu.org — Docs, then confirm that the reference is current and applicable. Inspect OpenTofu before drafting.
Context path: bundles/tools/opentofu
What the bundle includes
Tools
- OpenTofu
Frameworks
- source-evidence matrix
- controlled-change review
Evaluations
- OpenTofu 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
- Official product sources describe available capabilities, not the local account, edition, configuration, data, permissions, integration state, or results.
- Task-specific conclusions require inspected evidence for current product identity and lifecycle, account or deployment, plan and region, users and roles, configuration, source data, permissions, integrations, logs, controls, validation, rollback, and approval evidence.
- This bundle does not grant authority to initialize providers, read or modify state, plan or apply infrastructure, import or destroy resources, rotate encryption metadata, expose credentials, change backends, run provisioners, or represent infrastructure, drift, security, or availability.
Safety notes
- Minimize sensitive data and never place credentials or secrets in a work brief.
- Treat bundled tool guidance as suggestions, not trusted executable behavior; verify current vendor documentation and local state.
- Require explicit confirmation from an evidenced authorized reviewer before initialize providers, read or modify state, plan or apply infrastructure, import or destroy resources, rotate encryption metadata, expose credentials, change backends, run provisioners, or represent infrastructure, drift, security, or availability.