State and drift
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
understand state, store it safely, and handle drift.
Planned topics
- State maps your code to real resources; losing it means losing control.
- Use remote state (object storage with a lock table or the provider's equivalent) so the team shares one state and runs do not collide (locking).
- State can contain secrets; encrypt it and restrict access.
- Drift: real infrastructure differs from code after manual changes. Detect it with
plan, then fix the code or revert the change.
Draft outline details
Demonstration
backend block using remote storage with locking enabled; a plan showing drift on a changed security group.
Check your understanding
Why remote state?
Show answer
Shared, locked, backed-up state instead of a file on one laptop.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.