Orthevs Orthevs Fathom new horizons
Menu

Workshop wiki · English

Curriculum: Terraform

This curriculum structures a Terraform workshop from fundamentals to advanced platform and security operations. It combines theory, architecture understanding, practical exercises, review criteria and operational maturity.

Content language · EnglishSize · 72.9 KBdocs/curriculum-terraform-EN.md
Workshop examples as ZIP files
Learning progress in the web app

Mark chapters as read, view reading progress and check off practice modules after enabling the optional web app. Workshop progress is calculated from chapters across all document pages. Your choices stay on this device; there is no account or server sync. Installation is not required. Withdrawing your choice in Privacy settings deletes the progress.

Reading progress0%
0%
0 / 9 chapters read
Other language versionGerman ↗Greek ↗

Curriculum: Terraform

This curriculum structures a Terraform workshop from fundamentals to advanced platform and security operations. It combines theory, architecture understanding, practical exercises, review criteria and operational maturity.

Curriculum Goal

After the full series you can design, review, operate and safely evolve Terraform configurations in teams. You understand providers, state, backends, modules, plan artifacts, HCP Terraform, Terraform Enterprise, governance and incident response.

01 / 09

Teaching Model

The workshop follows a repeating cycle:

text
Understand -> Write -> Plan -> Review -> Apply -> Operate -> Secure
Step Goal Typical Activity
Concept understand purpose and limits IaC model, provider, state, backend
Configuration describe desired state HCL, variables, locals, resources
Plan make impact visible terraform plan, JSON plan, diff review
Review evaluate risks state, secrets, destroy, IAM, cost
Apply execute in a controlled way approval, locking, remote run, audit
Operations handle drift, recovery and changes runbook, import, state migration
02 / 09

Level Structure

Level Focus Outcome
Fundamentals IaC, HCL, Provider, Resources, Variablen, Outputs, lokaler State und sicherer CLI-Workflow You can explain, locally check and operationally review the included Terraform patterns.
Intermediate Module, Backends, Remote State, Locking, for_each, lifecycle, Import und Refactoring You can explain, locally check and operationally review the included Terraform patterns.
Professional Multi-Environment-Design, Modulversionierung, CI/CD, Drift, HCP Terraform, TACOS und Governance You can explain, locally check and operationally review the included Terraform patterns.
Advanced Security State Security, Least Privilege, Supply Chain, Policy as Code, Destroy-Schutz und Incident Response You can explain, locally check and operationally review the included Terraform patterns.
03 / 09

Roles and Learning Paths

  • Developers focus on HCL, modules, inputs, outputs and CI feedback.
  • Platform engineers focus on backends, module registry, workspaces, remote runs and governance.
  • SREs focus on drift, locks, recovery, audit and change control.
  • Security engineers focus on state, secrets, provider supply chain, policy as code and credential leaks.
04 / 09

Lab Strategy

All labs run locally without production credentials. HCL artifacts use local provider patterns and static checks; real cloud applies are deliberately unnecessary.

05 / 09

Assessment Rubric

Criterion Basic Good Excellent
Correctness HCL is readable and structured providers and variables are cleanly set plan/state impact is explained
Security no secrets in code state and backend risks are marked recovery and rotation are described
Operations manual execution possible CI and review path exists governance and audit are included
Architecture single project understood module and environment boundaries clear organization model with HCP/TFE/TACOS can be reviewed
06 / 09

Sources and References

07 / 09

Review Checklist for Curriculum

  • 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.
  • 53. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
  • 54. review module boundary: Record the affected module, provider, resource, state and backend path.
  • 55. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
  • 56. produce drift evidence: Record the affected module, provider, resource, state and backend path.
  • 57. mark secret risk: Record the affected module, provider, resource, state and backend path.
  • 58. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
  • 59. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
  • 60. write team rule: Record the affected module, provider, resource, state and backend path.
  • 61. document configuration and target state: Record the affected module, provider, resource, state and backend path.
  • 62. review provider requirement: Record the affected module, provider, resource, state and backend path.
  • 63. explain state impact: Record the affected module, provider, resource, state and backend path.
  • 64. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
08 / 09

Practice Appendix: Curriculum

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. IaC

  • Task: document configuration and target state and connect the observation explicitly to IaC.
  • 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. 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.

A003. Provider

  • Task: explain state impact and connect the observation explicitly to Provider.
  • 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. Backend

  • Task: describe backend and locking model and connect the observation explicitly to Backend.
  • 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. Module

  • Task: review module boundary and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: evaluate variable and output and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: produce drift evidence and connect the observation explicitly to Security.
  • 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. IaC

  • Task: mark secret risk and connect the observation explicitly to IaC.
  • 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. 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.

A011. Provider

  • Task: record rollback or recovery path and connect the observation explicitly to Provider.
  • 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. 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.

A013. Backend

  • Task: document configuration and target state and connect the observation explicitly to Backend.
  • 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. Module

  • Task: review provider requirement and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: explain state impact and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: evaluate plan diff and connect the observation explicitly to Security.
  • 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. IaC

  • Task: describe backend and locking model and connect the observation explicitly to IaC.
  • 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. 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.

A019. Provider

  • Task: evaluate variable and output and connect the observation explicitly to Provider.
  • 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. 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.

A021. Backend

  • Task: mark secret risk and connect the observation explicitly to Backend.
  • 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. Module

  • Task: name policy or CI gate and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: record rollback or recovery path and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • 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. IaC

  • Task: document configuration and target state and connect the observation explicitly to IaC.
  • 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. 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.

A027. Provider

  • Task: explain state impact and connect the observation explicitly to Provider.
  • 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. 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.

A029. Backend

  • Task: describe backend and locking model and connect the observation explicitly to Backend.
  • 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. Module

  • Task: review module boundary and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: evaluate variable and output and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: produce drift evidence and connect the observation explicitly to Security.
  • 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. IaC

  • Task: mark secret risk and connect the observation explicitly to IaC.
  • 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. 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.

A035. Provider

  • Task: record rollback or recovery path and connect the observation explicitly to Provider.
  • 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. 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.

A037. Backend

  • Task: document configuration and target state and connect the observation explicitly to Backend.
  • 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. Module

  • Task: review provider requirement and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: explain state impact and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: evaluate plan diff and connect the observation explicitly to Security.
  • 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. IaC

  • Task: describe backend and locking model and connect the observation explicitly to IaC.
  • 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. 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.

A043. Provider

  • Task: evaluate variable and output and connect the observation explicitly to Provider.
  • 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. 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.

A045. Backend

  • Task: mark secret risk and connect the observation explicitly to Backend.
  • 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. Module

  • Task: name policy or CI gate and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: record rollback or recovery path and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • 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. IaC

  • Task: document configuration and target state and connect the observation explicitly to IaC.
  • 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. Provider

  • Task: explain state impact and connect the observation explicitly to Provider.
  • 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. 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.

A053. Backend

  • Task: describe backend and locking model and connect the observation explicitly to Backend.
  • 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. Module

  • Task: review module boundary and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: evaluate variable and output and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: produce drift evidence and connect the observation explicitly to Security.
  • 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. IaC

  • Task: mark secret risk and connect the observation explicitly to IaC.
  • 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. 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.

A059. Provider

  • Task: record rollback or recovery path and connect the observation explicitly to Provider.
  • 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. Backend

  • Task: document configuration and target state and connect the observation explicitly to Backend.
  • 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. Module

  • Task: review provider requirement and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: explain state impact and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: evaluate plan diff and connect the observation explicitly to Security.
  • 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. IaC

  • Task: describe backend and locking model and connect the observation explicitly to IaC.
  • 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. 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.

A067. Provider

  • Task: evaluate variable and output and connect the observation explicitly to Provider.
  • 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. 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.

A069. Backend

  • Task: mark secret risk and connect the observation explicitly to Backend.
  • 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. Module

  • Task: name policy or CI gate and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: record rollback or recovery path and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • 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. IaC

  • Task: document configuration and target state and connect the observation explicitly to IaC.
  • 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. 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.

A075. Provider

  • Task: explain state impact and connect the observation explicitly to Provider.
  • 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. 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.

A077. Backend

  • Task: describe backend and locking model and connect the observation explicitly to Backend.
  • 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. Module

  • Task: review module boundary and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: evaluate variable and output and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: produce drift evidence and connect the observation explicitly to Security.
  • 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. IaC

  • Task: mark secret risk and connect the observation explicitly to IaC.
  • 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. 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.

A083. Provider

  • Task: record rollback or recovery path and connect the observation explicitly to Provider.
  • 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. 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.

A085. Backend

  • Task: document configuration and target state and connect the observation explicitly to Backend.
  • 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. Module

  • Task: review provider requirement and connect the observation explicitly to Module.
  • 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. CI/CD

  • Task: explain state impact and connect the observation explicitly to CI/CD.
  • 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. Security

  • Task: evaluate plan diff and connect the observation explicitly to Security.
  • 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. IaC

  • Task: describe backend and locking model and connect the observation explicitly to IaC.
  • 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. 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.

A091. Provider

  • Task: evaluate variable and output and connect the observation explicitly to Provider.
  • 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. 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.

A093. Backend

  • Task: mark secret risk and connect the observation explicitly to Backend.
  • 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.

A094. Module

  • Task: name policy or CI gate and connect the observation explicitly to Module.
  • 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.

A095. CI/CD

  • Task: record rollback or recovery path and connect the observation explicitly to CI/CD.
  • 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.

A096. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • 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.

A097. IaC

  • Task: document configuration and target state and connect the observation explicitly to IaC.
  • 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.

A098. 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.

A099. Provider

  • Task: explain state impact and connect the observation explicitly to Provider.
  • 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.

A100. 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.

A101. Backend

  • Task: describe backend and locking model and connect the observation explicitly to Backend.
  • 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.

A102. Module

  • Task: review module boundary and connect the observation explicitly to Module.
  • 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.

A103. CI/CD

  • Task: evaluate variable and output and connect the observation explicitly to CI/CD.
  • 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.

A104. Security

  • Task: produce drift evidence and connect the observation explicitly to Security.
  • 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.

A105. IaC

  • Task: mark secret risk and connect the observation explicitly to IaC.
  • 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.

A106. 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.

A107. Provider

  • Task: record rollback or recovery path and connect the observation explicitly to Provider.
  • 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.

A108. 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.

A109. Backend

  • Task: document configuration and target state and connect the observation explicitly to Backend.
  • 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.

A110. Module

  • Task: review provider requirement and connect the observation explicitly to Module.
  • 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.

A111. CI/CD

  • Task: explain state impact and connect the observation explicitly to CI/CD.
  • 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.

A112. Security

  • Task: evaluate plan diff and connect the observation explicitly to Security.
  • 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.
09 / 09

TFM · Orthevs Academy

31 modules as one continuous learning path.

The sequence remains unchanged: from the lab skeleton through technical foundations and operating models to final troubleshooting. The technical directory names are deliberately preserved.

Practice modules

Orthevs as an app

Install Orthevs

The Orthevs web app can be installed on supported mobile devices and desktop browsers.

iPhone and iPad

Open Orthevs in Safari. Tap Share, then Add to Home Screen. Enable Open as Web App if offered, then tap Add.

Android

For the web app, open the browser menu and choose Install app or Add to Home screen. Confirm the installation.

Desktop browser

Open the browser menu or the install icon in the address bar, then choose Install app or Add to Dock.

Web app installation depends on your browser. If no install prompt appears, follow the browser steps shown above.