{"id":115470,"date":"2024-05-01T12:46:45","date_gmt":"2024-05-01T10:46:45","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-opentofu-1-7-forka-platformy-upravleniya-konfiguracziej-terraform"},"modified":"2024-05-01T12:46:45","modified_gmt":"2024-05-01T10:46:45","slug":"vypusk-opentofu-1-7-forka-platformy-upravleniya-konfiguracziej-terraform","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-opentofu-1-7-forka-platformy-upravleniya-konfiguracziej-terraform","title":{"rendered":"Release of OpenTofu 1.7, a fork of the configuration management platform Terraform","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of OpenTofu 1.7 has been announced, continuing the development of the open-source code base for configuration management and infrastructure automation platform Terraform. OpenTofu is being developed under the auspices of the Linux Foundation using an open governance model with participation from a community formed by companies and enthusiasts interested in the project (support for the project has been declared by 161 companies and 792 individual developers). The project code is written in Go and is distributed under the MPL 2.0 license. <\/p>\n
The fork was created in response to HashiCorp's transition of its products to the proprietary BSL 1.1 license, which restricts the use of code in cloud systems competing with HashiCorp's products and services. The change in licensing is motivated by the desire to maintain funding for its developments in an environment where traditional licensing models struggle to counteract companies leveraging HashiCorp's open-source works to create their own commercial cloud products without participating in collaborative development. <\/p>\n
The platform can be used for building, modifying, and versioning infrastructure in line with the infrastructure as code concept, where system configurations are described in a high-level domain-specific language and processed similarly to code. OpenTofu supports the construction of a resource graph, defining all relationships between resources for efficient parallel operations and changes considering dependencies. <\/p>\n
OpenTofu also allows generating an Execution Plan based on the specified configuration, enabling assessment of infrastructure actions prior to their actual implementation. Complex changes to the infrastructure can be executed automatically, with minimal administrator involvement, thus avoiding many human-error-induced mistakes. The administrator can fully track what will be changed and in what order, utilizing the provided execution plan and resource graph. <\/p>\n
Among the changes in version OpenTofu 1.7: <\/p>\n
\n
The ability to protect critical state files using end-to-end encryption. Encryption ensures that unauthorized entities cannot access these files when using untrusted storage backends. The encryption password can be set using environment variables or key management systems like AWS KMS, GCP KMS, and OpenBao.\n
Support for provider-defined dynamic functions. This capability allows providers to offer not only resources but also functions for use in OpenTofu code. Moreover, functions can be defined dynamically by the provider based on user configuration. Support for this functionality has already been added to the experimental Lua and Go providers.\n
Declarative delete operations have been implemented, allowing you to mark a resource for deletion from the state file while preserving it in the created infrastructure.\n
The ability to use «for_each» loops in blocks that perform imports, simplifying the importation of multiple standard resources. <\/ul>\n