M365Con 2027 – כנס אונליין חינמי · 11–22 Jan 2027 · 120 sessions m365con.net

OpenTofu

Product

OpenTofu is an open source infrastructure-as-code tool forked from Terraform after HashiCorp moved Terraform to the Business Source License. It is governed by the Linux Foundation under the MPL 2.0 license.

◆ PRODUCTOpenTofuM365.FM
Title graphic: OpenTofu (Product)

נושאים שנדונים גם

בפרק על OpenTofu עולים גם: Bicep what-if, Resource drift, Terraform state, Azure Verified Modules, Azure Resource Manager ו-Developer experience (DX).

Description

OpenTofu is an open source infrastructure-as-code (IaC) tool that began as a fork of Terraform. The fork was started by Gruntwork, Spacelift, Harness, env0, Scalr and others after HashiCorp moved Terraform from an open source license to the Business Source License, which the project describes as ambiguous for companies and developers. OpenTofu is governed by the Linux Foundation and is released under the MPL 2.0 license. Its website describes it as a drop-in replacement for Terraform that preserves existing workflows and configurations.

Infrastructure as code means describing cloud resources in configuration files instead of creating them by hand, so that environments can be deployed repeatedly and consistently. OpenTofu is used for this purpose. According to its website, it manages resources across clouds through providers, and the site gives examples such as AWS S3 buckets, Cloudflare DNS records and GitHub repositories. The project cites an ecosystem of more than 3,900 providers and 23,600 modules, and a registry search site lets users look up providers and modules.

The project describes itself as community driven and aims for feature parity with Terraform. Contributions come through GitHub discussions, issues, RFC reviews and code, and the website credits more than 180 community contributors along with sponsors who support hosting and monitoring. Because it sits under the Linux Foundation's stewardship, the direction of the tool is not tied to a single vendor.

The website highlights several features by release. Version 1.7 introduced client-side state encryption, with key providers such as PBKDF2, AWS KMS, GCP KMS and OpenBao. Version 1.8 added early evaluation of variables and locals in module sources. Version 1.9 added the -exclude flag and provider for_each. These items show the project's focus on state protection, module flexibility and provider handling, although the sources do not describe them in more detail.

Typical decisions around OpenTofu concern licensing and compatibility. Teams that already have Terraform configurations may weigh a tool that keeps existing workflows against the license terms of the original product. Teams starting new IaC work on a cloud platform will also compare it with other options, since several tools exist for the same job.

In the M365.FM episode "Infrastructure as Code - Simply Explained", OpenTofu appears in a list of widely used IaC tools for Azure. The listed tools are Terraform, OpenTofu, ARM Templates, Bicep Templates, Ansible, Pulumi, Chef and SaltStack. The episode excerpt goes on to explain ARM templates, which use JSON files to define and deploy Azure resources, so OpenTofu is mentioned there as one option among several rather than examined in depth.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeProduct

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Maintained by Mirko Peters (Microsoft MVP) · Last updated: