World map

 

BM

World T4: Modules & Pipelines

When not to use IaC

You will learn: what belongs in a blueprint, what doesn't, and what to do after an emergency click.

Checked with OpenTofu 1.13 on 1 Nov 2026

The problem

You need one test bucket for ten minutes. Then you delete it. Do you write a blueprint first?

Try it

Does each one belong in a blueprint?

Drag a card into a box. Or tap the card, then tap the box.

      Predict

      Outage at 3am. You fix it by clicking in the cloud console. What should happen the next morning?

      Check

      Put the after-emergency steps in order.

      First step at the top. Put these in order. Use the arrows, or drag.

      • Plan: it should say No changes
      • Put it in the blueprint, or adopt it with an import block
      • Fix the outage first
      • Merge it, with a review
      • Write down what you clicked

      Check

      Swipe: a good habit, or needs work?

      Swipe right for good, left for needs work. Or use the buttons.

      1 / 4

      Blueprint the things you would hate to rebuild by hand

      You did it!

      You can now choose when a blueprint helps, and when it gets in the way.

      Go deeper (optional)

      IaC is great for things that last, repeat or need review. It is weak for data and very short experiments. It also clashes with things another tool owns, like a Deployment managed by Argo CD. One owner per thing is the rule.