Why infrastructure as code
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
see why infrastructure belongs in version control.
Planned topics
- Clicking in a console is slow, undocumented, and cannot be reproduced.
- Code gives review, history, repeatable environments, and disaster recovery.
- Declarative tools (Terraform, OpenTofu, Pulumi, Bicep, CloudFormation) describe the end state; the tool computes the steps.
- Treat infrastructure changes like application changes: pull request, review, pipeline.
Draft outline details
Demonstration
the MID-056 console steps versus the same environment as a short code file.
Check your understanding
What does "declarative" mean?
Show answer
You describe the desired end state; the tool works out how.
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.