Orthevs Orthevs Fathom new horizons
Menu

Workshop wiki · English

Remote State Data Source (EN)

This example is a controlled Terraform lab. It contains HCL artifacts, a local module, test data and a run.sh that performs static checks and evidence generation.

Content language · EnglishSize · 37.0 KBexamples/17-remote-state-data-source/docs/en/README.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 / 6 chapters read
Other language versionGerman ↗Greek ↗

Remote State Data Source (EN)

Focus: Remote-State-Konsum und Kopplungsrisiken.

Purpose

This example is a controlled Terraform lab. It contains HCL artifacts, a local module, test data and a run.sh that performs static checks and evidence generation.

01 / 06

Local Check

bash
./run.sh
02 / 06

Learning Goals

  • trace Terraform configuration
  • review provider requirements
  • explain state and backend impact
  • inspect evidence files
  • derive review rules
03 / 06

Files

04 / 06

Review Checklist for Remote State Data Source

  • 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.
05 / 06

Practice Appendix: Remote State Data Source

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. Remote-State-Konsum und Kopplungsrisiken

  • Task: document configuration and target state and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review provider requirement and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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

A005. Remote-State-Konsum und Kopplungsrisiken

  • Task: describe backend and locking model and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review module boundary and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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. Remote-State-Konsum und Kopplungsrisiken

  • Task: mark secret risk and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

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

A011. State

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

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

A013. Remote-State-Konsum und Kopplungsrisiken

  • Task: document configuration and target state and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review provider requirement and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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. Remote-State-Konsum und Kopplungsrisiken

  • Task: describe backend and locking model and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review module boundary and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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

A021. Remote-State-Konsum und Kopplungsrisiken

  • Task: mark secret risk and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: name policy or CI gate and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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. Remote-State-Konsum und Kopplungsrisiken

  • Task: document configuration and target state and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review provider requirement and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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

A029. Remote-State-Konsum und Kopplungsrisiken

  • Task: describe backend and locking model and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review module boundary and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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. Remote-State-Konsum und Kopplungsrisiken

  • Task: mark secret risk and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: name policy or CI gate and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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

A037. Remote-State-Konsum und Kopplungsrisiken

  • Task: document configuration and target state and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

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

A039. State

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

A040. 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. Remote-State-Konsum und Kopplungsrisiken

  • Task: describe backend and locking model and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review module boundary and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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

A045. Remote-State-Konsum und Kopplungsrisiken

  • Task: mark secret risk and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: name policy or CI gate and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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. Remote-State-Konsum und Kopplungsrisiken

  • Task: document configuration and target state and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review provider requirement and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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

A053. Remote-State-Konsum und Kopplungsrisiken

  • Task: describe backend and locking model and connect the observation explicitly to Remote-State-Konsum und Kopplungsrisiken.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. Terraform

  • Task: review module boundary and connect the observation explicitly to Terraform.
  • Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which credentials, state values, provider 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. State

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

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.