Your plan says (known after apply). OpenTofu 1.13 lets you talk back
Every person who has reviewed an infrastructure plan knows the feeling. You run tofu plan on a Friday afternoon. The output scrolls past. A third of the values you actually care about say the same thing: + id = ( known after apply ) So you squint. You reason from experience. You say "yes, that looks right" to a plan that is, in the strictest sense, guessing. Then you apply, and the guessing…
Infrastructure plans can be uncertain, leaving readers squinting at unknown values. OpenTofu 1.13 aims to make these plans more transparent. The planner used to guess values it couldn't determine during the planning phase, but now you can tell the planner what you know. By using functions like assumenotnull, assumestringprefix, and assumeequal, module authors can explicitly state assumptions about values that are only determined after the remote system acts.
This allows downstream validations to run during the planning phase itself, before any resources are created. If an assumption turns out to be false during the apply phase, the plan will fail, preventing silent breakage. The release also introduces built-in linting, symbol libraries, and Windows on ARM64 support. Unknowns in infrastructure plans can cause problems for automated checks and policy enforcement.
The new features in OpenTofu 1.13 give module authors a way to explicitly state assumptions about values, sharpening the plan's vision and allowing teams to identify and address uncertainty before it becomes a problem.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
