OpenTofu 1.7.0 is out with State Encryption, Dynamic Provider-defined Functions
In the last few months since our first stable release the OpenTofu community and the core team have worked hand in hand to bring functionality to OpenTofu that has been requested for years. We are proud to announce the immediate availability of OpenTofu 1.7.0, bringing you the following highlights:
- End-to-end state encryption protects your state file from prying eyes, no matter what storage backend you use. You can provide your encryption passphrase securely using environment variables, or use a key management system such as AWS KMS, GCP KMS, or OpenBao. This feature has been developed in collaboration with Stephan Bartels (Interhyp) and Alex Scheel from the OpenTofu community, whom we would like to thank for their work on this feature.
- Dynamic provider-defined functions let a provider not only provide resources, but also native functions you can use in your OpenTofu code. What's more, we added an OpenTofu-only feature to let providers dynamically define custom functions based on your configuration. This enhancement allows you to fully integrate other programming languages as shown in our live stream. You can try out this functionality with our experimental Lua and Go providers.
- The removed block lets you mark OpenTofu-created resources for removal from the state file, but still keep the infrastructure you created.
- Loopable import blocks let you bulk-import resources declaratively in your OpenTofu code, helping with large-scale migrations.
As with the previous version, OpenTofu remains a drop-in replacement for its predecessor Terraform™ 1.5 and has easy migration paths from later versions. Check out the overhauled migration guides for detailed migration instructions. You can find the full list of changes and comprehensive examples in the documentation.
Since the first release, the OpenTofu community and adoption have been growing significantly. While we don't believe in tracking our users and don't have accurate numbers, we have seen a constant month-over-month growth in our registry usage since our launch only 4 months ago. Over just the last month our registry usage has more than doubled to well over a million requests per day.
Additionally, we had 65 unique contributors for this release alone and have recently reached 20,000 stars on GitHub. Since January, we have seen our community spread the word about OpenTofu, open over 200 new issues and file even more pull requests.
If you are new to OpenTofu, welcome! We started as a fork of HashiCorp's Terraform™ after its license was changed to the restrictive BUSL alongside a frequently changing licensing FAQ. OpenTofu is an infrastructure-as-code tool that lets you declaratively create cloud infrastructure with thousands of APIs by writing your own code or using one of the tens of thousands of community-provided modules.
For example, you could create an EC2 instance on AWS like this:
resource "aws_instance" "web" {
ami = "add AMI ID here"
instance_type = "t3.micro"
}
OpenTofu's main advantage is that it records any changes to your cloud infrastructure in a state file, which allows it to later modify the same infrastructure, or tear it down if you created it as a test.
OpenTofu is first and foremost a community-driven project. We are looking forward to the continued tradition of working on issues the community deems important. For transparency and to encourage everyone to vote, we have created a list of the most upvoted issues.
While much of OpenTofu 1.8 is still in planning, we are currently finalizing a proposal for a feature that lets you use variables as module sources, backend configuration, and more. Early evaluation of variables has been requested in over 30 issues so far and is one of the most-requested features in OpenTofu.
If you have a feature you would like to see in OpenTofu, please don't hesitate to open an issue or reach out to us on Slack.