Skill · Provisioning · Reason about and maintain infrastructure as code, whatever the tool
Evolve an existing infrastructure in code: import, drift, replacement and destruction
Bring a hand-built infrastructure under code until the plan is empty, choose a drift detection cadence and decide to reconcile, overwrite or exclude a gap, protect a resource from destruction, replace it without downtime and recover from an interrupted apply.
Start lesson 1The Provisioning domain
- 3 lessons
- ~1 h 15 of reading
- 3 quizzes
- 0 proof lab
The path
Where it comes from, where it leads
What you need to know first, where you stand on this skill, and what it opens next. Your status is computed in your browser, from what you have read and passed.
Before · 1 prerequisite
Recommended before · 1
This skill, for you
Evolve an existing infrastructure in code: import, drift, replacement and destruction
Computing
It unlocks · nothing yet
No other skill requires it: it is an end-of-path skill.
The path through the foundations From the most upstream foundation to this skill: what is in place, what remains to read.
Lessons
How to learn it
3 lessons, about ~1 h 15, in program order. Each lesson ends with its quiz.
The program
3 lessons · ~1 h 15
Beyond the lessons
Assess, practise, pass the proof
Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.
Assess yourself
3 quizzes
At the end of the lessons: passed at 70%, they confirm the skill.
Practice
No guided lab
No guided lab practices it yet.
Proof
No proof
Neither a challenge nor a mission with a proof yet.
Placement test
Preparing the questions…
Your answers in detail
For each question asked: your answer, the correct answer, its explanation and the page to reread.
Around it
Who requires it, who teaches it
Required by
Taught by
Same block · Reason about and maintain infrastructure as code, whatever the tool
- Predict what an IaC tool will create, change or destroy: declarative model, idempotence, state and plan
- Choose an IaC approach and record the decision: provision or configure, change or replace, push or pull
- Choose the IaC tool family that fits the problem: resources, configuration, images, language
- Keep an IaC repository healthy: layered structure, plan review, testing pyramid and secrets out of the code
- Structure infrastructure as code at scale: stacks, versioned modules, environments and debt
- Deliver infrastructure as code under control: approved plan, policies, engine identity and cost