opentofu/CHANGELOG.md at 0170ed606cdfbca38577ebebe21d524f77f07906

mirror of https://github.com/opentofu/opentofu.git synced 2024-12-24 16:10:46 -06:00

Martin Atkins 0170ed606c

2022-11-02 09:09:06 -07:00

1.4.0 (Unreleased)

BUG FIXES:

The module installer will now record in its manifest a correct module source URL after normalization when the URL given as input contains both a query string portion and a subdirectory portion. Terraform itself doesn't currently make use of this information and so this is just a cosmetic fix to make the recorded metadata more correct. [GH-31636]
When installing remote module packages delivered in tar format, Terraform now limits the tar header block size to 1MiB to avoid unbounded memory usage for maliciously-crafted module packages. [GH-32135]
Terraform will now reject excessively-complex regular expression patterns passed to the regex, regexall, and replace functions, to avoid unbounded memory usage for maliciously-crafted patterns. This change should not affect any reasonable patterns intended for practical use. [GH-32135]
Terraform on Windows now rejects invalid environment variables whose values contain the NUL character when propagating environment variables to a child process such as a provider plugin. Previously Terraform would incorrectly treat that character as a separator between two separate environment variables. [GH-32135]

ENHANCEMENTS:

The "Failed to install provider" error message now includes the reason a provider could not be installed. [GH-31898]
backend/gcs: Add kms_encryption_key argument, to allow encryption of state files using Cloud KMS keys. [GH-24967]
backend/gcs: Add storage_custom_endpoint argument, to allow communication with the backend via a Private Service Connect endpoint. [GH-28856]
backend/gcs: Update documentation for usage of gcs with terraform_remote_state [GH-32065]

EXPERIMENTS:

Since its introduction the yamlencode function's documentation carried a warning that it was experimental. This predated our more formalized idea of language experiments and so wasn't guarded by an explicit opt-in, but the intention was to allow for small adjustments to its behavior if we learned it was producing invalid YAML in some cases, due to the relative complexity of the YAML specification.

From Terraform v1.4 onwards, yamlencode is no longer documented as experimental and is now subject to the Terraform v1.x Compatibility Promises. There are no changes to its previous behavior in v1.3 and so no special action is required when upgrading.

For information on prior major and minor releases, see their changelogs: