#opentofu (2024-12)
Discuss OpenTofu-related topics
2024-12-05
prepare for v1.7.7 release (#2254) Signed-off-by: ollevche [email protected] (<mailto:[email protected]>)
Signed-off-by: ollevche [email protected]
v1.8.7: prepare for 1.8.7 release (#2255) Signed-off-by: ollevche [email protected] (<mailto:[email protected]>)
Signed-off-by: ollevche [email protected]
v1.7.7 BUG FIXES:
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 <a href=”https://github.com/opentofu/opentofu/pull/2179” data-hovercard-type=”pull_request”…
Signed-off-by: ollevche [email protected]
Currently when using a remote state storage configuration, if the encryption method is changed a null_resource, output or similar state change is required to apply the encryption change. This has …
ImportantThis fix is for the sake of security scanners only. The vulnerable code (ParseWithClaims) is not used anywhere in OpenTofu or its dependencies outside of test cases.
Bumps github.com/gola…
v1.8.7 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 (<a href=”https://github.com/opentofu/opentofu/pull/2232” data-hovercard-type=”pull_request”…
OpenTofu Version OpenTofu v1.8.5 on linux_amd64 OpenTofu Configuration Files variable “passphrase” { type = string sensitive = true nullable = false validation { condition = length(var.passphrase) …
prepare for v1.9.0-beta1 (#2258) Signed-off-by: ollevche [email protected] (<mailto:[email protected]>)
Signed-off-by: ollevche [email protected]
v1.9.0-beta1 Do not use this release for production workloads! It’s time for the beta release of the 1.9.0 version! This 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…
Do not use this release for production workloads! It’s time for the beta release of the 1.9.0 version! This includes a lot of major and minor new features, as well as a ton of community contr…
2024-12-09
v1.9.0-beta2: Bump version to 1.9.0-beta2 (#2271) Signed-off-by: Christian Mesh [email protected] (<mailto:[email protected]>)
Signed-off-by: Christian Mesh [email protected]
v1.9.0-beta2 Do not use this release for production workloads! This build fixes a bug where destroy would not always function correctly with provider for_each. It’s time for the beta release of the 1.9.0 version! This 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…
Do not use this release for production workloads! This build fixes a bug where destroy would not always function correctly with provider for_each. It’s time for the beta release of the 1.9.0 …