OpenTofu: baixar versions anteriors

BUG FIXES:
- tofu show -json <planfile> now works again when ephemeral resources are present in the configuration. (4623).
- Ephemeral output values are now always re-evaluated during the apply phase, instead of sometimes using stale values from the planning phase. (#4582)

OpenTofu 1.13.0
We're proud to announce that OpenTofu 1.13.0 is now officially available! 🎉

Highlights

Windows on ARM64 is now a supported platform
Starting with OpenTofu v1.13.0 we are now offering official packages targeting Windows on the ARM64 (also known as "aarch64") CPU architecture.

Reducing unknowns during planning
OpenTofu v1.13 introduces a number of new functions that are all intended to allow module authors to give OpenTofu additional hints about what they know to be true even though OpenTofu cannot infer it automatically.

Linting Experiment
OpenTofu v1.13 includes some very early work towards built-in "linting" features in OpenTofu, although we are hoping to eventually incorporate other similar needs such as policy enforcement into a single comprehensive feature.

Symbol Libraries Experiment
We're considering a new kind of artifact called a "Symbol Library", which is a reusable collection of values, functions, and type aliases that can be imported from all of the same source types that are already supported for modules.

Compatibility Notes
- base64gzip produces results that are equivalent but not byte-for-byte identical to previous versions, this is due to a required golang version upgrade
- WinRM is no longer supported for provisioners
- macOS: Requires macOS 13 Ventura or later
- OpenTofu v1.13 will be the last series that includes official releases for 32 bit CPUs

Reference
- Full Changelog
- Blog Post
Thank you for your continued support and testing of the OpenTofu project!

SECURITY ADVISORIES:
- When interacting with OCI Distribution registries for module or provider package installation, earlier versions of OpenTofu could incorrectly resend credentials intended for the original origin to the target of an HTTP redirect. (#4422)
- When interacting with an attacker-controlled remote state backend or provider/module registry, tofu init in earlier versions of OpenTofu could potentially cause high CPU usage and/or high memory usage resolving crafted relative URLs in the API responses. (#4472)

SECURITY ADVISORIES:
- Previous releases in the v1.12 series could be affected by several vulnerabilities:
- The Encrypted Client Hello implementation (which is used by OpenTofu through the go stdlib) would leak the pre-shared key identities during the handshake,
allowing a passive network observer who can collect handshakes to de-anonymize the hostname of the server, even when ECH was being used.
This is fixed now by (#4363)
BUG FIXES:
- Fixed bug where implicit moves and provider address changes would incorrectly cause providers.MovedResourceState to be used in place of providers.UpgradeResourceState (#4375)

BUG FIXES:
- tofu plan -out no longer fails when the plan includes a resource with lifecycle { destroy = false } that needs replacement, which previously errored with invalid change action ForgetThenCreate. (#4324)
- Moved block now correctly compares provider source addresses. (#4280)[https://github.com//pull/4280]
- Correct Source Provider Address now passed into Provider MoveResource requests. (#4355)[https://github.com//pull/4355]

BUG FIXES:
- Properly handle TF_ENCRYPTION with only blank spaces. (#4265)
- The value resulted from the lifecycle.enabled evaluation now has its deprecation marks processed correctly (#4162)
- Update documentation to clarify the usage restriction of ephemeral values in lifecycle.enabled. (#4220)
- tofu console -lock=false now works as intended. (#4291)

SECURITY ADVISORIES:
- Previous releases in the v1.12 series could read an arbitrary file during certain git operations via a maliciously crafted URL (#4293)

1.12.2
SECURITY ADVISORIES:
- Previous releases in the v1.12 series could be affected by several vulnerabilities:
- If for state encryption, OpenBao key provider is used with wrapping algorithms, it could generate panics or hangs on compromised systems where the JWE is specifically crafted.
This is fixed now by (#4177)
- Previous releases in the v1.12 series could be affected by several vulnerabilities:
- When using SSH connections through OpenTofu, the errors that were returned from attempting a connection could include unescaped input bytes.
- If using an attacker-controlled server to run tofu against, it might end up in high CPU consumption.
These are now fixed by (#4247)
BUG FIXES:
- Properly handle EDEADLK during provider installation. On Unix systems, the kernel may erroneously detect a deadlock between tofu processes using the global plugin cache. (#4166)
- Fix race condition while handling closing signals during tofu login, both when the signal is sent by the user and when the browser fails to successfully connect. (4016)
- Prevent panic when using ephemeral resources during tofu test`. (#4254)

SECURITY ADVISORIES:
- Previous releases in the v1.12 series could be affected by several vulnerabilities:
- ssh usage through OpenTofu generate hangs or panics.
- Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.
This is fixed now by (#4145)

BUG FIXES:
- Address a bug introduced in v1.12.0 causing excessive memory usage by providers. (#4126)
- Address a bug introduced in v1.12.0 where replace_triggered_by was validated incorrectly. (#4133
- The Azure key provider will now accept the tenant_id, subscription_id, environment, and metadata_host variables; a bug previously only allowed these to be set through environment variables. (#4091)
Full Changelog: https://github.com/opentofu/opentofu/blob/v1.12/CHANGELOG.md

OpenTofu 1.12.0
We're proud to announce that OpenTofu 1.12.0 is now officially available! 🎉

Highlights
This release cycle introduces major new capabilities and integrations:

Dynamic prevent_destroy
OpenTofu v1.12.0 now allows prevent_destroy to be defined dynamically in terms of other values available elsewhere in the same module. For example:
variable "prevent_destroy_database" {
type = bool
default = true
}
resource "example_database" "example" {
# ...
lifecycle {
prevent_destroy = var.prevent_destroy_database
}
}

Provider Checksum Improvements
The default provider installation behavior in OpenTofu is designed to mostly "just work" by getting the needed providers installed and making the necessary changes to the dependency lock file, but in previous versions friction appeared for any teams using many of the non-default installation settings such as the shared provider plugin cache, or local mirrors of upstream providers.
For OpenTofu v1.12, OpenTofu Registry now provides a full set of official checksums in all of the checksum formats needed by other installation methods. This means that after running tofu init the dependency lock file will immediately have all of the information required to successfully use a global plugin cache directory and to verify matching packages served from a local mirror, without needing to run tofu providers lock separately.

Simultaneous Human-readable and Machine-readable Output
Many OpenTofu commands support both human-oriented UI output and machine-readable JSON output, but previously those commands could be run with only one or the other. This was bothersome for those implementing alternative UIs in terms of the machine-readable output because it meant they would need to implement all possible features of the UI before their tool could actually be used.
OpenTofu v1.12.0 introduces a new option -json-into=FILENAME, which produces the same output format that -json would have produced but sends that output to the given filename instead of to the standard output stream. The OpenTofu UI output then appears on the standard output stream as normal, so that software interpreting the JSON output can behave as just a supplement to the normal UI rather than a complete replacement.

New destroy lifecycle meta-argument
The new destroy = false lifecycle option for managed resources allows removing an object from the state without first destroying the remote object.

Deprecation Notices

WinRM for Provisioners is Now Deprecated
Some of the Go libraries that OpenTofu uses for WinRM connection support in provisioners have become unmaintained over time, and so unfortunately we are phasing out support for WinRM in OpenTofu starting with deprecation warnings in this release.
If your configuration includes a connection block with type = "winrm" then OpenTofu v1.12 will warn that this connection type is deprecated, but provisioning should otherwise still work as it did before.
We intend to remove WinRM support completely in the forthcoming OpenTofu v1.13 series, and so if you are currently relying on WinRM support we recommend that you begin planning to migrate to using OpenSSH for Windows instead.

Phasing Out Support for 32-bit CPU Architectures
We are also planning to stop producing official releases for 32-bit CPU architectures (386 and arm) in a future version of OpenTofu. Support for 64-bit architectures (amd64 and arm64) is unaffected.
OpenTofu v1.12 does not include any changes to CPU support yet, but we expect that the official builds in the forthcoming v1.13 series will begin producing warnings when running on 32-bit CPU architectures, before we stop producing those packages altogether in a future release series.

Compatibility Notes
- macOS: Requires macOS 12 Monterey or later
- The OPENTOFU_USER_AGENT environment variable, which allowed fully overriding the default User-Agent header on all HTTP requests, has been removed.
- On Unix systems OpenTofu now considers the BROWSER environment variable as a

BUG FIXES:
- Running tofu apply -refresh-only with a configuration that contains ephemeral resources does not fail anymore because the refresh produced changes (#3776)
- Fixed tofu init crashing when a module version uses a variable and the module is referenced from a test file. (#3686)
- Fixed provider-defined functions in import block id expressions causing "BUG: Uninitialized function provider" error. (#3803)
- tofu test no longer fails during cleanup when using a mocked version of a resource type with write-only attributes. (#3964)
- A malicious remote TLS server can no longer deadlock OpenTofu by sending multiple key update messages in a single record. (#3966)
- When installing module packages from "tar" archives, OpenTofu now accepts only a limited number of sparse file entries to avoid unbounded memory usage from maliciously-crafted archives containing many sparse regions. (#3966)
Full Changelog: v1.11.5...v1.11.6

BUG FIXES:
- Add universe_domain option in the gcs backend to support sovereign GCP services (#3758)
- The azurerm backend's MSI authentication method will now respect the provided client ID (#3586)
- Using a network mirror for the providers source does not print debug logs without being asked for (#3736)
Full Changelog: https://github.com/opentofu/opentofu/blob/67fe9db49b7dafd46470cf9ac7f437aaa95f5c40/CHANGELOG.md

SECURITY ADVISORIES:
- Previous releases in the v1.11 series could potentially take an excessive amount of time processing a maliciously-crafted .zip archive during either provider or module installation during tofu init. (#3689)
BREAKING CHANGES:
- Modules containing local provider configurations now also reject the enabled argument, matching existing behavior for count, for_each, and depends_on. (#3680)
This was an oversight in the original design of the enabled feature and was missed during the review process. Although our goal is to not introduce breaking changes in patch releases, in some cases it may be warranted. Anyone who has used the enabled feature in this particular way will have unintentionally introduced a foot-gun into their infrastructure and should remedy it post-haste.
BUG FIXES:
- In JSON syntax, the state encryption method configuration now allows specifying keys using both normal expression syntax and using template interpolation syntax. Previously only the template interpolation syntax was allowed, which was inconsistent with other parts of the encryption configuration. (#3654)
- Providers are not configured anymore with DeferralAllowed capability of OpenTofu since having that created unwanted behaviour from some providers. (#3676)
- Resources containing write-only attributes now are rendered consistently during planning. (#3667)
Full Changelog: v1.11.3...v1.11.4

BUG FIXES:
- Fix crash when the executed configuration contains an import block that points to unexisting configuration block (#3616)
- Fixed tofu test with mock_provider failing during cleanup when lifecycle { ignore_changes } references a block. (#3644)
- Fixed state lock not being released when tofu apply is interrupted with Ctrl+C while using the HTTP backend. (#3624)
- azure backend: resolve OIDC token dynamically to support ADO refresh. (#3594)
Full Changelog: v1.11.2...v1.11.3

UPGRADE NOTES:
- The change from #2643, that was announced previously in v1.11.0, has been reverted in this release. OpenTofu will no longer directly recommend using the -exclude= option to work around problems caused by unknown values in provider configurations.
Unfortunately there are existing providers that spuriously report that they cannot plan due to unknown values even when planning would have been successful, and so we cannot rely on providers to accurately signal when unknown values are the cause of an error. Using -exclude is still a valid workaround for these problems even though OpenTofu cannot accurately detect when it's useful to make that suggestion.
BUG FIXES:
- Fix crash in plan -generate-config-out with read-only nested attributes (#3553)
- It's now possible again to plan changes with the hashicorp/helm and hashicorp/kubernetes providers when the provider configuration contains unknown values, as long as the configuration is carefully written to avoid the plan phase actually depending on those values. (#3592)
- When running tofu init on Windows with an azurerm backend, the subscription_id is quoted correctly allowing successful authentication. (#3602)
- Fix serialization error in apply when using cloud backend (#3611)
Full Changelog: v1.11.1...v1.11.2

BUG FIXES:
- Fixed regression where import validation would incorrectly flag variables used in for_each statements within import blocks (#3564)
- Fixed lifecycle enabled serialization in plan file (#3566)
- Fixed regression when validating import.id expressions (#3567)
Full Changelog: v1.11.0...v1.11.1

OpenTofu 1.11.0
We're proud to announce that OpenTofu 1.11.0 is now officially available! 🎉
Highlights
This release cycle introduces major new capabilities and integrations:
Ephemeral Values and Write Only Attributes
Ephemeral resources allow you to work with confidential data, temporary credentials, and transient infrastructure without persisting them to your state.
ephemeral "aws_secretsmanager_random_password" "password" {
}
resource "kubernetes_secret_v1" "credentials" {
metadata {
name = "admin"
namespace = "my-app"
}
data_wo = {
username = "admin"
password = ephemeral.aws_secretsmanager_random_password.password.random_password
}
data_wo_revision = 1
type = "kubernetes.io/basic-auth"
}
The enabled Meta-Argument
If you want to conditionally deploy a resource, you no longer have to use count = var.create_my_resource ? 1 : 0, you can now add the new enabled meta-argument to your resource to conditionally deploy it.
resource "aws_instance" "web" {
ami = "ami-12345"
instance_type = "t3.micro"
lifecycle {
enabled = var.create_instance # Simple boolean condition
}
}
Compatibility Notes
- macOS: Requires macOS 12 Monterey or later
- Azure Backend (azurerm):
- The endpoint and ARM_ENDPOINT configuration options are no longer supported
- The msi_endpoint and ARM_MSI_ENDPOINT options are no longer supported
- The environment and metadata_host arguments are now mutually exclusive
- issensitive() Function: Now correctly returns unknown results when evaluating unknown values. Code that previously relied on the incorrect behavior may need updates.
- Testing with Mocks: Mock values generated during testing now strictly adhere to provider schemas. Test configurations with invalid mock values will need to be corrected.
- S3 Module Installation: When installing module packages from Amazon S3 buckets using S3 source addresses OpenTofu will use the same credentials as the AWS CLI and SDK.
- TLS and SSH Security:
- SHA-1 signatures are no longer accepted for TLS or SSH connections
- SSH certificates must comply with the draft-miller-ssh-cert-03 specification
Reference
- Full Changelog
- Blog Post
Thank you for your continued support and testing of the OpenTofu project!

SECURITY ADVISORIES:
This release contains fixes for some security advisories related to previous releases in this series.
- Incorrect handling of excluded subdomain constraint in conjunction with TLS certificates containing wildcard SANs
This release incorporates the upstream fixes for GO-2025-4175.
- Excessive CPU usage when reporting error about crafted TLS certificate with many hostnames
This release incorporates the upstream fixes for GO-2025-4155.
Full Changelog: v1.10.7...v1.10.8

SECURITY ADVISORIES:
This release contains fixes for some security advisories related to previous releases in this series.
- tofu init in OpenTofu v1.10.6 and earlier could potentially use unbounded memory if there is a direct or indirect dependency on a maliciously-crafted module package distributed as a "tar" archive.
This would require the attacker to coerce a root module author to depend (directly or indirectly) on a module package they control, using the HTTP, Amazon S3, or Google Cloud Storage source types to refer to a tar archive.
This release incorporates the upstream fixes for CVE-2025-58183.
- When making requests to HTTPS servers, OpenTofu v1.10.6 and earlier could potentially use unbounded memory or crash with a "panic" error if TLS verification involves an excessively-long certificate chain or a chain including DSA public keys.
This affected all outgoing HTTPS requests made by OpenTofu itself, including requests to HTTPS-based state storage backends, module registries, and provider registries. For example, an attacker could coerce a root module author to depend (directly or indirectly) on a module they control which then refers to a module or provider from an attacker-controlled registry. That mode of attack would cause failures in tofu init, at module or provider installation time.
Provider plugins contain their own HTTPS client code, which may have similar problems. OpenTofu v1.10.7 cannot address similar problems within provider plugins, and so we recommend checking for similar advisories and fixes in the provider plugins you use.
This release incorporates upstream fixes for CVE-2025-58185, CVE-2025-58187, and CVE-2025-58188.
BUG FIXES:
- Fix crash in tofu test when using deprecated outputs (#3249)
- Fix missing provider functions when parentheses are used (#3402)
- for_each inside dynamic blocks can now call provider-defined functions. (#3429)
Full Changelog: v1.10.6...v1.10.7

1.10.6
UPGRADE NOTES:
- Upgrade go from 1.24.4 to 1.24.6 to fix GO-2025-3849 (3127)
- Upgrade github.com/openbao/openbao/api/v2 from 2.1.0 to 2.3.0 to fix GO-2025-3783 (3134)
- The upgrade is necessary to silence the security scanner and does not affect the actual state encryption provided by OpenBao.
BUG FIXES:
- Variables with validation no longer interfere with the destroy process (#3131)
- Fixed crash when processing multiple deprecated marks on a complex object (#3105)
- When OpenTelemetry encounters errors, log it at the warning level instead of panic (#3235)
Full Changelog: v1.10.5...v1.10.6

BUG FIXES:
- Fixed issue where usage of TF_PLUGIN_CACHE_DIR could result in unexpected lock contention errors (#3090)
- NOTE: It is still highly recommended to have valid .terraform.lock.hcl files in projects using TF_PLUGIN_CACHE_DIR
Full Changelog: v1.10.4...v1.10.5

BUG FIXES:
- Fixed crash where sensitive set values used in for_each could cause a panic. (#3070)
- Fixed incorrect approach to mocking provider "ReadResource" calls in test. (#3068)
- Reduced calls to ListKeys in azure backend (for rate limiting). (#3083)
Full Changelog: v1.10.3...v1.10.4

1.10.3
BUG FIXES:
- OpenTofu will no longer crash in a rare case where a dynamically-invalid expression has its error suppressed by try or can and then that expression becomes relevant for deciding whether to report a "change outside of OpenTofu" in the human-oriented plan diff. (#2988)
- Ensure provider downloads into temp are cleaned up correctly on windows. (#2843)
- Correctly handle structural typed attributes during test provider mocking. (#2994)
- Fix erroneous detection of changes with sensitive resource attributes. (#3024)
Full Changelog: v1.10.2...v1.10.3

What's Changed
- Fix TF_APPEND_USER_AGENT handling in the S3 remote state backend in #2955
- go.mod: Upgrade to Go 1.24.4 by @apparentlymart in #2927
Full Changelog: v1.10.0...v1.10.1

OpenTofu 1.10.0
We're thrilled to announce the release of OpenTofu 1.10.0, our most comprehensive update yet! This release represents months of dedicated work from our community, introducing some fantastic features that will improve how OpenTofu users manage and distribute infrastructure as code.
Highlights
This release cycle introduces major new capabilities and integrations:
OCI Registry Support
Full integration with OCI registries for both provider and module distribution, valuable for organizations with private infrastructure-as-code components, air-gapped environments, or enhanced security requirements.
# Configure OCI registry mirrors in your CLI configuration:
provider_installation {
oci_mirror {
repository_template = "example.com/opentofu-providers/${namespace}/${type}"
include = ["registry.opentofu.org/*/*"]
}
}
# Use OCI modules directly in your configuration:
module "vpc" {
source = "oci://example.com/modules/vpc/aws"
}
Native S3 Locking
Simplify your infrastructure by using S3's conditional writes capability for state locking, eliminating the need for a separate DynamoDB table.
terraform {
backend "s3" {
bucket = "tofu-state-backend"
key = "statefile"
region = "us-east-1"
use_lockfile = true # Enable native S3 locking
}
}
OpenTelemetry Tracing
Gain insights into OpenTofu operations with experimental OpenTelemetry tracing, completely local and under your control.
# Launch a tracing backend like Jaeger
docker run -d --name jaeger \
-p 16686:16686 -p 4317:4317 \
jaegertracing/jaeger:2.5.0
# Configure OpenTofu to use OpenTelemetry
export OTEL_TRACES_EXPORTER=otlp
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317
export OTEL_EXPORTER_OTLP_INSECURE=true
# Run your operations and view traces at http://localhost:16686
tofu init
Resource Management with Target Files
Manage complex deployments more easily with the new -target-file and -exclude-file options, allowing version-controlled resource targeting patterns.
# Create a targets.txt file
# Critical infrastructure components
module.networking.aws_vpc.main
module.networking.aws_subnet.public[*]
# Apply only those resources
tofu apply -target-file=targets.txt
# Similarly, create an excludes.txt file to skip certain resources
tofu plan -exclude-file=excludes.txt
Compatibility Notes
- Linux: Requires kernel version 3.2 or later
- macOS: Requires macOS 11 Big Sur or later
- The ghcr.io/opentofu/opentofu image is no longer supported as a base image
- Windows: Symbolic links and junctions are now handled differently
- The PostgreSQL backend in OpenTofu 1.10 should not be used alongside older versions
Reference
- Full Changelog
- GitHub Comparison: v1.9.0...v1.10.0
- Blog Post

BUG FIXES:
- Provider used in import is correctly identified. (#2336)
- plantimestamp() now returns unknown value during validation (#2397)
- Syntax error in the required_providers block does not panic anymore, but yields "syntax error" (2344)
- Fix the error message when default value of a complex variable is containing a wrong type (2394)
- Changing Go version to 1.22.11 in order to fix CVE-2024-45336 and CVE-2024-45341 (#2438)
- Fix the way OpenTofu downloads a module that is sourced from a GitHub branch containing slashes in the name. (2396)
- Changing Go version to 1.22.12 in order to fix CVE-2025-22866 and CVE-2024-45341 (#2438)
Full Changelog: v1.9.0...v1.9.1

We're proud to announce that OpenTofu 1.9.0 is now officially out! 🎉This release includes a lot of major and minor new features, as well as a ton of community contributions!The highlights are:
- for_each in provider configuration blocks: An alternate (aka "aliased") provider configuration can now have multiple dynamically-chosen instances using the for_each argument:
provider "aws" {
alias = "by_region"
for_each = var.aws_regions

region = each.key
}

Each instance of a resource can also potentially select a different instance of the associated provider configuration, making it easier to declare infrastructure that ought to be duplicated for each region.
- -exclude planning option: similar to -target, this allows operators to tell OpenTofu to work on only a subset of the objects declared in the configuration or tracked in the state.
tofu plan -exclude=kubernetes_manifest.crds

While -target specifies the objects to include and skips everything not needed for the selected objects, -exclude instead specifies objects to skip. OpenTofu will exclude the selected objects and everything that depends on them.
Please take the above for a spin and let us know your feedback!For all the features, see the detailed changelog.You can find the full diff here.

SECURITY:
- Upgraded golang.org/x/crypto to resolve CVE-2024-45337. (#2287)
- Upgraded golang.org/x/net to resolve CVE-2024-45338. (#2311)
BUG FIXES:
- tofu test now removes outputs of destroyed modules between different test runs. (#2274)

BUG FIXES:
- Error messages related to validation of sensitive input variables will no longer disclose the sensitive value in the UI. (#2219)
- Changes to encryption configuration now auto-apply the migration (#2232)
- Updated github.com/golang-jwt/jwt/v4 from 4.4.2 to 4.5.1 to make security scanners happy (no vulnerability, see #2179)
- tofu test is now setting nulls for dynamic type when generating mock values. (#2245)
- Variables declared in test files are now taking into account type default values. (#2244)

ENHANCEMENTS:
- OpenTofu builds now use Go version 1.22 (#2050)
BUG FIXES:
- Extended trace logging for HTTP backend, including request and response bodies. (#2120)
- The tofu test command doesn't try to validate mock provider definition by its underlying provider schema now. (#2140)
- Type validation for mocks and overrides are now less strict in tofu test. (#2144)

BUG FIXES:
- Provider functions will now handle partially unknown arguments per the tfplugin spec (#2127)
- tofu init will no longer return a spurious "Backend configuration changed" error when re-initializing a working directory with existing initialization of a backend whose configuration schema has required arguments. This was a regression caused by the similar fix in the v1.8.4 release. (#2135)
Full Changelog: https://github.com/opentofu/opentofu/compare/v1.8.4...v1.8.5

BUG FIXES:
- tofu init will no longer return a supurious "Backend configuration changed" error when re-initializing a working directory with identical settings, backend configuration contains references to variables or local values, and when the -backend-config command line option is used. That combination previously caused OpenTofu to incorrectly treat the backend configuration as invalid. (#2055)
- configuration generation should no longer fail when generating sensitive properties
- Provider defined functions are now supported better in child modules
- Fixed an issue where X-Terraform-Get was not being read correctly if a custom module registry returns a 200 statuscode instead of 201
Full Changelog: https://github.com/opentofu/opentofu/compare/v1.8.3...v1.8.4

What's Changed
SECURITY:
- Update go version to 1.21.11 to fix CVE-2024-24790
BUG FIXES:
- Better handling of key_provider references (#1965)
Full Changelog: https://github.com/opentofu/opentofu/compare/v1.8.1...v1.8.2

What's Changed
- Fix missing module source panic (#1888) in #1889
Full Changelog: https://github.com/opentofu/opentofu/compare/v1.8.0...v1.8.1

We're proud to announce that OpenTofu 1.8.0 is now officially out! 🎉What's New?
- Early variable/locals evaluation
- Provider mocking in tofu test
- Resource overrides in tofu test
- Override files for OpenTofu: keeping compatibility
- Deprecation: use_legacy_workflow has been removed from the S3 backend-backend
See the launch post on our blog: https://opentofu.org/blog/opentofu-1-8-0/For all the features, see the detailed changelog.You can find the full diff here.

OpenTofu 1.7.3 is now out!The main improvement is a bug fix for handling lower-case proxy environment variables.If you'd like to read about all the changes introduced, check out the detailed changelog.

We're proud to announce that OpenTofu 1.7.2 is now officially out 🎉This is a bugfix release and we encourage all OpenTofu 1.7.1 users to upgrade.What’s New?
- Fixed - authorization header is not included for HTTP backends (
- Fixed bug in import 'to' parsing in JSON configurations (
- Fix bug where provider functions were unusable in variables and outputs (
For all the features, see the detailed changelog.You can find the full diff here.

We're proud to announce that OpenTofu 1.7.1 is now officially out!This is a bugfix release and we encourage all OpenTofu 1.7.0 users to upgrade.What’s New?- Fixed support for provider functions in tests (#1603)
- Fixed crash in gcs backend when using certain commands (#1618)
- Fix inmem backend crash due to missing struct field (#1619)
- Fix for tofu init failure when tests have spaces in their name. (#1489)
- tofu test now supports accessing module outputs when the module has no resources. (#1409)
For all the features, see the detailed changelog.You can find the full diff here.

We're proud to announce that OpenTofu 1.7.0 is now officially out! 🎉What’s New?- State Encryption - Protect your precious state files with end-to-end encryption.
- Dynamic Provider-defined Functions - Author custom functions as part of providers.
- Declarative removed Blocks - No more fighting with the CLI, execute your removals declaratively!
- Loopable Import Blocks - Streamline importing multiple resources.
- ...and much, much more!
See the launch post on our blog: https://opentofu.org/blog/opentofu-1-7-0/For all the features, see the detailed changelog.You can find the full diff here.