OpenTofu lets you declaratively manage your cloud infrastructure.
- https://opentofu.org
OpenTofu lets you declaratively manage your cloud infrastructure.
| Release list | ||
|---|---|---|
| 1.11.2 | ||
| 1.11.1 | ||
| 1.11.0 | ||
| 1.10.8 | ||
| 1.10.7 | ||
| 1.10.6 | ||
| 1.9.4 | ||
| 1.10.5 | ||
| 1.10.4 | ||
| 1.9.3 | ||
| 1.8.11 | ||
| 1.7.10 | ||
| 1.7.9 | ||
| 1.8.10 | ||
| 1.9.2 | ||
| 1.10.3 | ||
| 1.10.2 | ||
| 1.10.1 | 6m+ | |
| 1.10.0 | 6m+ | |
| 1.9.1 | 6m+ | |
OpenTofu lets you declaratively manage your cloud infrastructure.
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:
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)tofu init on Windows with an azurerm backend, the subscription_id is quoted correctly allowing successful authentication. (#3602)Full Changelog: https://github.com/opentofu/opentofu/compare/v1.11.1...v1.11.2