Matt Gowie’s Post

Awesome TF functionality that only #OpenTofu supports: **Dynamic Backends** ⚡ With a couple of our clients, we see them utilize different backend state s3 buckets for each instance of their root modules e.g. they have a Dev, Stage, and Prod state bucket and use the `-backend-config=...` CLI arg to determine which state they're working on. This typically requires some script or wrapper for Terraform to do that type of dynamic "init with this backend bucket". But now... with OpenTofu v1.8+ and "Early Evaluation", that is a thing of the past! Check out the code in my screenshot below for what I'm referring to. With Terraform or prior to Tofu v1.8, you can't use variables in your backend config. But now that you can this means that you don't need to think about "did I init against the dev or the prod backend for this run?" -- You can instead just provide variable inputs in your tfvars files that define which backend you want to use. We got to recommend this to a new client recently and it was a BIG reduction to the overall complexity of their vanilla Tofu usage! Love to see new features from the OpenTofu team actually being used 🙌