Purpose

This example is a controlled Terraform workshop lab. It is safe for local execution and does not require cloud credentials.

Documentation

• Deutsch
• English

Files

• versions.tf
• main.tf
• variables.tf
• outputs.tf
• modules/naming/main.tf
• scenario.json
• run.sh

Run

./run.sh

The script writes temporary evidence below work/. The directory is ignored by Git.

Review Questions

• 1. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 2. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 3. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 4. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 5. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 6. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 7. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 8. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 9. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 10. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 11. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 12. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 13. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 14. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 15. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 16. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 17. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 18. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 19. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 20. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 21. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 22. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 23. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 24. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 25. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 26. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 27. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 28. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 29. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 30. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 31. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 32. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 33. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 34. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 35. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 36. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 37. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 38. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 39. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 40. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 41. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 42. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 43. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?
• 44. How does this example demonstrate Refactoring ohne State-Verlust with safe Terraform behavior?

Practice Appendix: Example Moved Blocks Refactoring

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. Refactoring ohne State-Verlust

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

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

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

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

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

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

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

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

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

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

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

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

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