Commands: Terraform
This document belongs to the Terraform workshop and describes commands 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
- terraform init
- fmt
- validate
- plan
- apply
- state
- import
- test
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
Review Checklist for Commands
- 01. document configuration and target state: Record the affected module, provider, resource, state and backend path.
- 02. review provider requirement: Record the affected module, provider, resource, state and backend path.
- 03. explain state impact: Record the affected module, provider, resource, state and backend path.
- 04. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
- 05. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
- 06. review module boundary: Record the affected module, provider, resource, state and backend path.
- 07. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
- 08. produce drift evidence: Record the affected module, provider, resource, state and backend path.
- 09. mark secret risk: Record the affected module, provider, resource, state and backend path.
- 10. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
- 11. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
- 12. write team rule: Record the affected module, provider, resource, state and backend path.
- 13. document configuration and target state: Record the affected module, provider, resource, state and backend path.
- 14. review provider requirement: Record the affected module, provider, resource, state and backend path.
- 15. explain state impact: Record the affected module, provider, resource, state and backend path.
- 16. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
- 17. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
- 18. review module boundary: Record the affected module, provider, resource, state and backend path.
- 19. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
- 20. produce drift evidence: Record the affected module, provider, resource, state and backend path.
- 21. mark secret risk: Record the affected module, provider, resource, state and backend path.
- 22. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
- 23. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
- 24. write team rule: Record the affected module, provider, resource, state and backend path.
- 25. document configuration and target state: Record the affected module, provider, resource, state and backend path.
- 26. review provider requirement: Record the affected module, provider, resource, state and backend path.
- 27. explain state impact: Record the affected module, provider, resource, state and backend path.
- 28. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
- 29. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
- 30. review module boundary: Record the affected module, provider, resource, state and backend path.
- 31. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
- 32. produce drift evidence: Record the affected module, provider, resource, state and backend path.
- 33. mark secret risk: Record the affected module, provider, resource, state and backend path.
- 34. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
- 35. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
- 36. write team rule: Record the affected module, provider, resource, state and backend path.
- 37. document configuration and target state: Record the affected module, provider, resource, state and backend path.
- 38. review provider requirement: Record the affected module, provider, resource, state and backend path.
- 39. explain state impact: Record the affected module, provider, resource, state and backend path.
- 40. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
- 41. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
- 42. review module boundary: Record the affected module, provider, resource, state and backend path.
- 43. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
- 44. produce drift evidence: Record the affected module, provider, resource, state and backend path.
- 45. mark secret risk: Record the affected module, provider, resource, state and backend path.
- 46. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
- 47. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
- 48. write team rule: Record the affected module, provider, resource, state and backend path.
- 49. document configuration and target state: Record the affected module, provider, resource, state and backend path.
- 50. review provider requirement: Record the affected module, provider, resource, state and backend path.
- 51. explain state impact: Record the affected module, provider, resource, state and backend path.
- 52. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
Practice Appendix: Commands
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. terraform init
- Task: document configuration and target state and connect the observation explicitly to
terraform init. - 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. fmt
- Task: review provider requirement and connect the observation explicitly to
fmt. - 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. validate
- Task: explain state impact and connect the observation explicitly to
validate. - 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. plan
- Task: evaluate plan diff and connect the observation explicitly to
plan. - 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. apply
- Task: describe backend and locking model and connect the observation explicitly to
apply. - 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. 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.
A007. import
- Task: evaluate variable and output and connect the observation explicitly to
import. - 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. test
- Task: produce drift evidence and connect the observation explicitly to
test. - 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. terraform init
- Task: mark secret risk and connect the observation explicitly to
terraform init. - 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. fmt
- Task: name policy or CI gate and connect the observation explicitly to
fmt. - 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. validate
- Task: record rollback or recovery path and connect the observation explicitly to
validate. - 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. plan
- Task: write team rule and connect the observation explicitly to
plan. - 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. apply
- Task: document configuration and target state and connect the observation explicitly to
apply. - 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. 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.
A015. import
- Task: explain state impact and connect the observation explicitly to
import. - 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. test
- Task: evaluate plan diff and connect the observation explicitly to
test. - 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. terraform init
- Task: describe backend and locking model and connect the observation explicitly to
terraform init. - 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. fmt
- Task: review module boundary and connect the observation explicitly to
fmt. - 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. validate
- Task: evaluate variable and output and connect the observation explicitly to
validate. - 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. plan
- Task: produce drift evidence and connect the observation explicitly to
plan. - 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. apply
- Task: mark secret risk and connect the observation explicitly to
apply. - 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. 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.
A023. import
- Task: record rollback or recovery path and connect the observation explicitly to
import. - 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. test
- Task: write team rule and connect the observation explicitly to
test. - 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. terraform init
- Task: document configuration and target state and connect the observation explicitly to
terraform init. - 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. fmt
- Task: review provider requirement and connect the observation explicitly to
fmt. - 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. validate
- Task: explain state impact and connect the observation explicitly to
validate. - 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. plan
- Task: evaluate plan diff and connect the observation explicitly to
plan. - 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. apply
- Task: describe backend and locking model and connect the observation explicitly to
apply. - 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. 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.
A031. import
- Task: evaluate variable and output and connect the observation explicitly to
import. - 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. test
- Task: produce drift evidence and connect the observation explicitly to
test. - 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. terraform init
- Task: mark secret risk and connect the observation explicitly to
terraform init. - 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. fmt
- Task: name policy or CI gate and connect the observation explicitly to
fmt. - 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. validate
- Task: record rollback or recovery path and connect the observation explicitly to
validate. - 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. plan
- Task: write team rule and connect the observation explicitly to
plan. - 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. apply
- Task: document configuration and target state and connect the observation explicitly to
apply. - 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. 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.
A039. import
- Task: explain state impact and connect the observation explicitly to
import. - 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. test
- Task: evaluate plan diff and connect the observation explicitly to
test. - 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. terraform init
- Task: describe backend and locking model and connect the observation explicitly to
terraform init. - 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. fmt
- Task: review module boundary and connect the observation explicitly to
fmt. - 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. validate
- Task: evaluate variable and output and connect the observation explicitly to
validate. - 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. plan
- Task: produce drift evidence and connect the observation explicitly to
plan. - 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. apply
- Task: mark secret risk and connect the observation explicitly to
apply. - 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. import
- Task: record rollback or recovery path and connect the observation explicitly to
import. - 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. test
- Task: write team rule and connect the observation explicitly to
test. - 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. terraform init
- Task: document configuration and target state and connect the observation explicitly to
terraform init. - 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. fmt
- Task: review provider requirement and connect the observation explicitly to
fmt. - 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. validate
- Task: explain state impact and connect the observation explicitly to
validate. - 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. plan
- Task: evaluate plan diff and connect the observation explicitly to
plan. - 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. apply
- Task: describe backend and locking model and connect the observation explicitly to
apply. - 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. 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.
A055. import
- Task: evaluate variable and output and connect the observation explicitly to
import. - 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. test
- Task: produce drift evidence and connect the observation explicitly to
test. - 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. terraform init
- Task: mark secret risk and connect the observation explicitly to
terraform init. - 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. fmt
- Task: name policy or CI gate and connect the observation explicitly to
fmt. - 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. validate
- Task: record rollback or recovery path and connect the observation explicitly to
validate. - 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. plan
- Task: write team rule and connect the observation explicitly to
plan. - 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. apply
- Task: document configuration and target state and connect the observation explicitly to
apply. - 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. 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.
A063. import
- Task: explain state impact and connect the observation explicitly to
import. - 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. test
- Task: evaluate plan diff and connect the observation explicitly to
test. - 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. terraform init
- Task: describe backend and locking model and connect the observation explicitly to
terraform init. - 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. fmt
- Task: review module boundary and connect the observation explicitly to
fmt. - 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. validate
- Task: evaluate variable and output and connect the observation explicitly to
validate. - 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. plan
- Task: produce drift evidence and connect the observation explicitly to
plan. - 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. apply
- Task: mark secret risk and connect the observation explicitly to
apply. - 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. 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.
A071. import
- Task: record rollback or recovery path and connect the observation explicitly to
import. - 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. test
- Task: write team rule and connect the observation explicitly to
test. - 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. terraform init
- Task: document configuration and target state and connect the observation explicitly to
terraform init. - 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. fmt
- Task: review provider requirement and connect the observation explicitly to
fmt. - 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. validate
- Task: explain state impact and connect the observation explicitly to
validate. - 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. plan
- Task: evaluate plan diff and connect the observation explicitly to
plan. - 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. apply
- Task: describe backend and locking model and connect the observation explicitly to
apply. - 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. 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.
A079. import
- Task: evaluate variable and output and connect the observation explicitly to
import. - 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. test
- Task: produce drift evidence and connect the observation explicitly to
test. - 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. terraform init
- Task: mark secret risk and connect the observation explicitly to
terraform init. - 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. fmt
- Task: name policy or CI gate and connect the observation explicitly to
fmt. - 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. validate
- Task: record rollback or recovery path and connect the observation explicitly to
validate. - 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. plan
- Task: write team rule and connect the observation explicitly to
plan. - 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. apply
- Task: document configuration and target state and connect the observation explicitly to
apply. - 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. 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.
A087. import
- Task: explain state impact and connect the observation explicitly to
import. - 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. test
- Task: evaluate plan diff and connect the observation explicitly to
test. - 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. terraform init
- Task: describe backend and locking model and connect the observation explicitly to
terraform init. - 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. fmt
- Task: review module boundary and connect the observation explicitly to
fmt. - 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. validate
- Task: evaluate variable and output and connect the observation explicitly to
validate. - 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. plan
- Task: produce drift evidence and connect the observation explicitly to
plan. - 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.