Plan-apply for environments: many technologies, one readable blueprint

TL;DR

A single environment is built from several different technologies (Terraform modules, Helm, and more) under one blueprint.

I designed the plan-apply view that makes that heterogeneous change legible enough to review and approve in seconds instead of squinting at raw plan output.

The problem

When one blueprint spans multiple tools, the naive result is a wall of undifferentiated plan text across technologies.

People could not tell at a glance what was being created, changed, or destroyed, across which technology, and the consequential lines drowned in noise. Approving that confidently is impossible, so people either stalled or rubber-stamped.

The insight

The unit of understanding is the change per module, grouped under the blueprint, with the consequence made legible before the detail.

Different technologies should read consistently even though their internals differ.

The solution

• Each technology resource (artifact) in the blueprint renders as its own expandable section with a completed or changed status, and inside it an attribute-level diff: the current value on the left, the new value or known after apply on the right, with add, change, and remove coloring and removed values called out.
• A run-stages timeline (initiated, planning, pending approval, installing, completed) shows exactly where the run is and how long each stage took, alongside cost estimation, the blueprint version, the collection, and who initiated it.
• The approval gate sits in the timeline, so a production change cannot proceed without a human.
• The view makes dependencies explicit, so you can see how a change to one resource affects the others it feeds (a security group flowing into an instance, an output feeding another module), not just each change in isolation.
• The same diff and stage language is reused across provision, promote, and teardown, so the review gesture is learned once.

Impact

Made a multi-technology plan reviewable at a glance, and put a human firmly in the loop for anything touching production.

Reflection

The hard part was not any single diff, it was designing one consistent grammar of what is about to change that holds across genuinely different technologies under a single blueprint.