Concepts: Terraform

This document belongs to the Terraform workshop and describes concepts as training material, reference documentation and review basis.

Target State

You should not treat Terraform as a mere plan/apply sequence, but as an infrastructure-as-code system: configuration describes desired state, providers translate it into API calls, state maps real objects to resource instances and backends enable collaboration. The critical questions are reproducibility, state security, provider pinning, reviewability and controlled change.

Focus

HCL
Resources
Data Sources
State
Backends
Modules
Workspaces

Core Terms

Term	Meaning
`Terraform`	HashiCorp infrastructure-as-code tool that plans and manages infrastructure through declarative configuration.
`HCL`	HashiCorp Configuration Language used for Terraform resources, providers, variables, outputs and modules.
`Configuration`	A set of Terraform files describing the infrastructure to manage.
`Root Module`	Top-level working directory where `terraform init`, `plan` and `apply` start.
`Provider`	Plugin connecting Terraform to an external system such as cloud, DNS, Kubernetes, SaaS or a local file resource.
`Resource`	Declaration of a managed infrastructure object with type, name and arguments.
`Data Source`	Read-only access to information from providers or external sources.
`Variable`	Module input value with type, default, validation and optional sensitive flag.
`Output`	Module output value visible to users or automation.
`Local Value`	Named expression inside a module to reduce repetition and complex expressions.
`State`	Persisted mapping between resource instances in configuration and real-world objects.
`Backend`	Storage and access model for state; some backends support locking and collaboration.
`Plan`	Preview of changes Terraform derives from configuration, state and provider information.
`Apply`	Execution of a saved or freshly calculated change against real infrastructure.
`Module`	Reusable collection of Terraform configuration with clear inputs and outputs.
`Workspace`	Terraform concept for multiple state instances with the same configuration; not a universal environment design substitute.
`HCP Terraform`	HashiCorp platform for remote runs, state, policies, teams, workspace management and governance.
`Terraform Enterprise`	Self-managed enterprise variant with similar governance and automation capabilities for organizations.
`TACOS`	TF Automation and Collaboration Software for remote execution, state, policies and collaboration.
`Policy as Code`	Automated rules for plan or configuration checks, for example in HCP Terraform, Sentinel, OPA or CI gates.

Reference Commands

# Projekt prüfen
terraform version
terraform fmt -check -recursive
terraform init -backend=false
terraform validate

# Änderungen planen und auswerten
terraform plan -out=tfplan
terraform show tfplan
terraform show -json tfplan

# State, Outputs und Tests prüfen
terraform state list
terraform output
terraform output -json
terraform test

# Gezielt und nur in Labs einsetzen
terraform import <adresse> <id>
terraform state mv <alt> <neu>
terraform init -migrate-state

Working Model

Describe desired state in a clearly scoped root module.
Pin Terraform and provider versions for the project.
Review variables, locals, modules, outputs and meta-arguments before the plan.
Support changes with terraform fmt, terraform validate, terraform plan, plan artifacts and review diffs.
Review state, backend, locking, credentials and sensitive outputs before each apply.
Document recovery: Git revert, state backup, import, state mv, secret rotation or provider correction.

Typical Decisions

Decision	Good Review Question	Risk if Wrong
Root module boundary	Which infrastructure should be planned and applied together?	too much blast radius or hidden dependencies
Backend	Who needs state access and which locking is required?	concurrent applies, state loss, secret leak
Provider version	Which API and provider version is approved?	unexpected plan diffs or breaking changes
Modules	Is reuse more important than direct readability?	unclear inputs, output coupling, hard debugging
Workspaces	Do they truly separate environments or only state names?	dev, staging and prod get mixed
HCP Terraform	Which runs, variables and policies should be centralized?	shadow automation or unclear ownership

Diagrams and Models

The diagrams are text-based on purpose so they remain reviewable without extra tooling.

Configuration -> init -> provider install -> plan -> review -> apply -> state update
                     |                       |                     |
                     v                       v                     v
                 lock file              plan artifact          backend/state

Root Module
  variables -> locals -> resources/data sources -> outputs
       |             |           |
       v             v           v
  child modules   providers   state bindings

CI Gate
  fmt -> init -backend=false -> validate -> plan -> policy -> approval -> apply

Operations Notes

State is security-sensitive and can contain sensitive values.
Backends store state; some support locking and some do not.
Saved plans and backend configuration may contain sensitive information.
Terraform CLI, HCP Terraform and Terraform Enterprise share the language but differ in runs, state, teams and governance.
License and ecosystem decisions belong in architecture and procurement processes, not in implicit tool assumptions.

Sources and References

Practice Appendix: Concepts

This appendix is a working backlog for longer trainings, reviews and repetitions. Each task can be checked locally with HCL artifacts and a Git repository.

A001. HCL

Task: document configuration and target state and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A002. Resources

Task: review provider requirement and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A003. Data Sources

Task: explain state impact and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A004. State

Task: evaluate plan diff and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A005. Backends

Task: describe backend and locking model and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A006. Modules

Task: review module boundary and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A007. Workspaces

Task: evaluate variable and output and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A008. HCL

Task: produce drift evidence and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A009. Resources

Task: mark secret risk and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A010. Data Sources

Task: name policy or CI gate and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A011. State

Task: record rollback or recovery path and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A012. Backends

Task: write team rule and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A013. Modules

Task: document configuration and target state and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A014. Workspaces

Task: review provider requirement and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A015. HCL

Task: explain state impact and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A016. Resources

Task: evaluate plan diff and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A017. Data Sources

Task: describe backend and locking model and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A018. State

Task: review module boundary and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A019. Backends

Task: evaluate variable and output and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A020. Modules

Task: produce drift evidence and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A021. Workspaces

Task: mark secret risk and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A022. HCL

Task: name policy or CI gate and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A023. Resources

Task: record rollback or recovery path and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A024. Data Sources

Task: write team rule and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A025. State

Task: document configuration and target state and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A026. Backends

Task: review provider requirement and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A027. Modules

Task: explain state impact and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A028. Workspaces

Task: evaluate plan diff and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A029. HCL

Task: describe backend and locking model and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A030. Resources

Task: review module boundary and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A031. Data Sources

Task: evaluate variable and output and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A032. State

Task: produce drift evidence and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A033. Backends

Task: mark secret risk and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A034. Modules

Task: name policy or CI gate and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A035. Workspaces

Task: record rollback or recovery path and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A036. HCL

Task: write team rule and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A037. Resources

Task: document configuration and target state and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A038. Data Sources

Task: review provider requirement and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A039. State

Task: explain state impact and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A040. Backends

Task: evaluate plan diff and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A041. Modules

Task: describe backend and locking model and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A042. Workspaces

Task: review module boundary and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A043. HCL

Task: evaluate variable and output and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A044. Resources

Task: produce drift evidence and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A045. Data Sources

Task: mark secret risk and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A046. State

Task: name policy or CI gate and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A047. Backends

Task: record rollback or recovery path and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A048. Modules

Task: write team rule and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A049. Workspaces

Task: document configuration and target state and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A050. HCL

Task: review provider requirement and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A051. Resources

Task: explain state impact and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A052. Data Sources

Task: evaluate plan diff and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A053. State

Task: describe backend and locking model and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A054. Backends

Task: review module boundary and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A055. Modules

Task: evaluate variable and output and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A056. Workspaces

Task: produce drift evidence and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A057. HCL

Task: mark secret risk and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A058. Resources

Task: name policy or CI gate and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A059. Data Sources

Task: record rollback or recovery path and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A060. State

Task: write team rule and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A061. Backends

Task: document configuration and target state and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A062. Modules

Task: review provider requirement and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A063. Workspaces

Task: explain state impact and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A064. HCL

Task: evaluate plan diff and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A065. Resources

Task: describe backend and locking model and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A066. Data Sources

Task: review module boundary and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A067. State

Task: evaluate variable and output and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A068. Backends

Task: produce drift evidence and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A069. Modules

Task: mark secret risk and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A070. Workspaces

Task: name policy or CI gate and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A071. HCL

Task: record rollback or recovery path and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A072. Resources

Task: write team rule and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A073. Data Sources

Task: document configuration and target state and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A074. State

Task: review provider requirement and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A075. Backends

Task: explain state impact and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A076. Modules

Task: evaluate plan diff and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A077. Workspaces

Task: describe backend and locking model and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A078. HCL

Task: review module boundary and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A079. Resources

Task: evaluate variable and output and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A080. Data Sources

Task: produce drift evidence and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A081. State

Task: mark secret risk and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A082. Backends

Task: name policy or CI gate and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A083. Modules

Task: record rollback or recovery path and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A084. Workspaces

Task: write team rule and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A085. HCL

Task: document configuration and target state and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A086. Resources

Task: review provider requirement and connect the observation explicitly to Resources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A087. Data Sources

Task: explain state impact and connect the observation explicitly to Data Sources.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A088. State

Task: evaluate plan diff and connect the observation explicitly to State.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A089. Backends

Task: describe backend and locking model and connect the observation explicitly to Backends.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A090. Modules

Task: review module boundary and connect the observation explicitly to Modules.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A091. Workspaces

Task: evaluate variable and output and connect the observation explicitly to Workspaces.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A092. HCL

Task: produce drift evidence and connect the observation explicitly to HCL.
Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
Security question: Which credentials, state values, provider versions or outputs would be critical?
Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.