OpenTofu 1.12.0, released May 14, 2026, is a quality-of-life release that resolves persistent friction in three common workflows. Teams managing infrastructure across multiple environments can now make destroy protection dynamic—keeping strict guardrails in production while staying flexible in development—without duplicating configuration. The long-standing tofu init lock file problem, which forced extra manual steps for teams using shared plugin caches or internal mirrors, is resolved automatically. And for platform teams building deployment tooling, a new CLI option finally lets machine-readable JSON output coexist with normal terminal logs, instead of replacing them. It's a release built around finishing things that were almost right.
All programming languages have a way to express and store values within the context of a code block. In the case of Terraform, that functionality is delivered through Terraform locals.
The release introduces several bug fixes, security improvements, and updates to documentation, the details of which you can find in our change log. Most importantly, it marks the introduction of our new OpenTofu public registry!
Terraform providers are essential to the functionality of Terraform. Learn how to install and use them to interact with diverse infrastructure services - AWS, Kubernetes,GitHub and more.
Pulumi lets you write infrastructure as code in TypeScript, Python, Go, and more. Updated for 2026: native Terraform/HCL support, Pulumi ESC, and env zero integration.
This post showcases the orchestration of Terraform deployments using Jenkins in a real-world scenario. It also delves into the pros and cons of choosing Jenkins for IaC management.
Learn how to combine our trio of capabilities — drift detection, scheduling, and approval policies — to automatically ensure consistent and compliant infrastructure.
Heading to KubeCon NA? Our team has got you covered with a guide on how to maximize your conference experience, including can’t-miss talks, networking events, and even places to explore in Chicago!
Developed out of one of our hackathons, this extension makes it easy to work with your env0 environments, making your development process faster and simpler.
What began as a mere idea and a handful of individuals burning the midnight oil to craft a manifesto just a few weeks ago has swiftly evolved into a full-fledged Linux Foundation project.
OpenTF became a focal point for extensive media coverage, heated debates, and insightful conversations. In this post, I’ll try to recap some of these, in a way that (I hope) would provide helpful context for people new to this story.
The latest milestone in the OpenTF journey is the release of OpenTF’s public repository. Within the first 12 hours, the repo already reached over 2,700 stars...
We’re proud to announce an open-source fork of Terraform called OpenTF. We also completed all documents to become part of the Linux Foundation. Details about the next steps and FAQs are inside.
On August 10th, HashiCorp made an important announcement, signaling a shift in its product licensing strategy. Here's what env0 customers need to know.
Essential building blocks of the Internet, such as Linux, Kubernetes, and Terraform need to be truly open source: that's the only way to ensure that we are building on top of solid and predictable underpinnings.
In this post, we'll walk through how GitHub Actions work, how to use them to automate Terraform operations, and how to embrace and enhance your current workflow.
One of the foundational commands at the heart of Terraform is terraform init. This command is what sets the stage for all the subsequent operations that you perform with Terraform. It prepares a new or existing directory for Terraform usage by creating initial files, loading any remote state, downloading modules, and installing provider plugins.