Update Terraform hashicorp/terraform to ~> 1.4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
hashicorp/terraform	required_version	minor	~> 1.3 -> ~> 1.4

---

Release Notes

hashicorp/terraform

v1.4.0

Compare Source

1.4.0 (March 08, 2023)

UPGRADE NOTES:

• config: The textencodebase64 function when called with encoding "GB18030" will now encode the euro symbol € as the two-byte sequence 0xA2,0xE3, as required by the GB18030 standard, before applying base64 encoding.

• config: The textencodebase64 function when called with encoding "GBK" or "CP936" will now encode the euro symbol € as the single byte 0x80 before applying base64 encoding. This matches the behavior of the Windows API when encoding to this Windows-specific character encoding.

• terraform init: When interpreting the hostname portion of a provider source address or the address of a module in a module registry, Terraform will now use non-transitional IDNA2008 mapping rules instead of the transitional mapping rules previously used.

  This matches a change to the WHATWG URL spec's rules for interpreting non-ASCII domain names which is being gradually adopted by web browsers. Terraform aims to follow the interpretation of hostnames used by web browsers for consistency. For some hostnames containing non-ASCII characters this may cause Terraform to now request a different "punycode" hostname when resolving.

• terraform init will now ignore entries in the optional global provider cache directory unless they match a checksum already tracked in the current configuration's dependency lock file. This therefore avoids the long-standing problem that when installing a new provider for the first time from the cache we can't determine the full set of checksums to include in the lock file. Once the lock file has been updated to include a checksum covering the item in the global cache, Terraform will then use the cache entry for subsequent installation of the same provider package. There is an interim CLI configuration opt-out for those who rely on the previous incorrect behavior. (#​32129)

• The Terraform plan renderer has been completely rewritten to aid with future Terraform Cloud integration. Users should not see any material change in the plan output between 1.3 and 1.4. If you notice any significant differences, or if Terraform fails to plan successfully due to rendering problems, please open a bug report issue.

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. (#​31636)
• config: The yamldecode function now correctly handles entirely-nil YAML documents. Previously it would incorrectly return an unknown value instead of a null value. It will now return a null value as documented. (#​32151)
• Ensure correct ordering between data sources and the deletion of managed resource dependencies. (#​32209)
• Fix Terraform creating objects that should not exist in variables that specify default attributes in optional objects. (#​32178)
• Fix several Terraform crashes that are caused by HCL creating objects that should not exist in variables that specify default attributes in optional objects within collections. (#​32178)
• Fix inconsistent behaviour in empty vs null collections. (#​32178)
• terraform workspace now returns a non-zero exit when given an invalid argument (#​31318)
• Terraform would always plan changes when using a nested set attribute (#​32536)
• Terraform can now better detect when complex optional+computed object attributes are removed from configuration (#​32551)
• A new methodology for planning set elements can now better detect optional+computed changes within sets (#​32563)
• Fix state locking and releasing messages when in -json mode, messages will now be written in JSON format (#​32451)

ENHANCEMENTS:

• terraform plan can now store a plan file even when encountering errors, which can later be inspected to help identify the source of the failures (#​32395)
• terraform_data is a new builtin managed resource type, which can replace the use of null_resource, and can store data of any type (#​31757)
• terraform init will now ignore entries in the optional global provider cache directory unless they match a checksum already tracked in the current configuration's dependency lock file. This therefore avoids the long-standing problem that when installing a new provider for the first time from the cache we can't determine the full set of checksums to include in the lock file. Once the lock file has been updated to include a checksum covering the item in the global cache, Terraform will then use the cache entry for subsequent installation of the same provider package. There is an interim CLI configuration opt-out for those who rely on the previous incorrect behavior. (#​32129)
• Interactive input for sensitive variables is now masked in the UI (#​29520)
• A new -or-create flag was added to terraform workspace select, to aid in creating workspaces in automated situations (#​31633)
• A new command was added for exporting Terraform function signatures in machine-readable format: terraform metadata functions -json (#​32487)
• The "Failed to install provider" error message now includes the reason a provider could not be installed. (#​31898)
• backend/gcs: Add kms_encryption_key argument, to allow encryption of state files using Cloud KMS keys. (#​24967)
• backend/gcs: Add storage_custom_endpoint argument, to allow communication with the backend via a Private Service Connect endpoint. (#​28856)
• backend/gcs: Update documentation for usage of gcs with terraform_remote_state (#​32065)
• backend/gcs: Update storage package to v1.28.0 (#​29656)
• When removing a workspace from the cloud backend terraform workspace delete will use Terraform Cloud's Safe Delete API if the -force flag is not provided. (#​31949)
• backend/oss: More robustly handle endpoint retrieval error (#​32295)
• local-exec provisioner: Added quiet argument. If quiet is set to true, Terraform will not print the entire command to stdout during plan. (#​32116)
• backend/http: Add support for mTLS authentication. (#​31699)
• cloud: Add support for using the generic hostname localterraform.com in module and provider sources as a substitute for the currently configured cloud backend hostname. This enhancement was also applied to the remote backend.
• terraform show will now print an explanation when called on a Terraform workspace with empty state detailing why no resources are shown. (#​32629)
• backend/gcs: Added support for GOOGLE_BACKEND_IMPERSONATE_SERVICE_ACCOUNT env var to allow impersonating a different service account when GOOGLE_IMPERSONATE_SERVICE_ACCOUNT is configured for the GCP provider. (#​32557)
• backend/cos: Add support for the assume_role authentication method with the tencentcloud provider. This can be configured via the Terraform config or environment variables.
• backend/cos: Add support for the security_token authentication method with the tencentcloud provider. This can be configured via the Terraform config or environment variables.

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.

v1.3.9

Compare Source

1.3.9 (February 15, 2023)

BUG FIXES:

• Fix crash when planning to remove already-deposed resource instances. (#​32663)

v1.3.8

Compare Source

1.3.8 (February 09, 2023)

BUG FIXES:

• Fixed a rare bug causing inaccurate before_sensitive / after_sensitive annotations in JSON plan output for deeply nested structures. This was only observed in the wild on the rancher/rancher2 provider, and resulted in glitched display in Terraform Cloud's structured plan log view. (#​32543)
• A variable only referenced by an output precondition error_message may be missing during evaluation (#​32464)
• Removing a NestingSingle block from configuration results in an invalid plan (#​32463)
• Null module outputs could be dropped, causing evaluation errors when referring to those module attributes (#​32583)
• Fix terraform crash when applying defaults into a collection with dynamic type constraint. (#​32454)
• Updated to newer github.com/mitchellh/cli version, in turn bringing in updates for several indirect dependencies with known security issues. (#​32609)
• Fix case where the first plan to use a new remote state could be applied twice, corrupting the state (#​32614)

v1.3.7

Compare Source

1.3.7 (January 04, 2023)

BUG FIXES:

• Fix exact version constraint parsing for modules using prerelease versions (#​32377)
• Prevent panic when a provider returns a null block value during refresh which is used as configuration via ignore_changes (#​32428)

v1.3.6

Compare Source

1.3.6 (November 30, 2022)

BUG FIXES:

• Terraform could crash if an orphaned resource instance was deleted externally and had condition checks in the configuration (#​32246)
• Module output changes were being removed and re-added to the stored plan, impacting performance with large numbers of outputs (#​32307)

v1.3.5

Compare Source

1.3.5 (November 17, 2022)

BUG FIXES:

• Prevent crash while serializing the plan for an empty destroy operation (#​32207)
• Allow a destroy plan to refresh instances while taking into account that some may no longer exist (#​32208)
• Fix Terraform creating objects that should not exist in variables that specify default attributes in optional objects. (#​32178)
• Fix several Terraform crashes that are caused by HCL creating objects that should not exist in variables that specify default attributes in optional objects within collections. (#​32178)
• Fix inconsistent behaviour in empty vs null collections. (#​32178)
• Prevent file uploads from creating unneeded temporary files when the payload size is known (#​32206)
• Nested attributes marked sensitive by schema no longer reveal sub-attributes in the plan diff (#​32004)
• Nested attributes now more consistently display when they become unknown or null values in the plan diff (#​32004)
• Sensitive values are now always displayed as (sensitive value) instead of sometimes as (sensitive) [GH32004]

v1.3.4

Compare Source

1.3.4 (November 02, 2022)

BUG FIXES:

• Fix invalid refresh-only plan caused by data sources being deferred to apply (#​32111)
• Optimize the handling of condition checks during apply to prevent performance regressions with large numbers of instances (#​32123)
• Output preconditions should not be evaluated during destroy (#​32051)
• Fix crash from console when outputs contain preconditions (#​32051)
• Destroy with no state would still attempt to evaluate some values (#​32051)
• Prevent unnecessary evaluation and planning of resources during the pre-destroy refresh (#​32051)
• AzureRM Backend: support for generic OIDC authentication via the oidc_token and oidc_token_file_path properties (#​31966)
• Input and Module Variables: Convert variable types before attempting to apply default values. (#​32027)
• 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. (#​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. (#​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. (#​32135)

v1.3.3

Compare Source

1.3.3 (October 19, 2022)

BUG FIXES:

• Fix error when removing a resource from configuration which has according to the provider has already been deleted. (#​31850)
• Fix error when setting empty collections into variables with collections of nested objects with default values. (#​32033)

v1.3.2

Compare Source

1.3.2 (October 06, 2022)

BUG FIXES:

• Fixed a crash caused by Terraform incorrectly re-registering output value preconditions during the apply phase (rather than just reusing the already-planned checks from the plan phase). (#​31890)
• Prevent errors when the provider reports that a deposed instance no longer exists (#​31902)
• Using ignore_changes = all could cause persistent diffs with legacy providers (#​31914)
• Fix cycles when resource dependencies cross over between independent provider configurations (#​31917)
• Improve handling of missing resource instances during import (#​31878)

v1.3.1

Compare Source

1.3.1 (September 28, 2022)

NOTE:

• On darwin/amd64 and darwin/arm64 architectures, terraform binaries are now built with CGO enabled. This should not have any user-facing impact, except in cases where the pure Go DNS resolver causes problems on recent versions of macOS: using CGO may mitigate these issues. Please see the upstream bug https://github.com/golang/go/issues/52839 for more details.

BUG FIXES:

• Fixed a crash when using objects with optional attributes and default values in collections, most visible with nested modules. (#​31847)
• Prevent cycles in some situations where a provider depends on resources in the configuration which are participating in planned changes. (#​31857)
• Fixed an error when attempting to destroy a configuration where resources do not exist in the state. (#​31858)
• Data sources which cannot be read during will no longer prevent the state from being serialized. (#​31871)
• Fixed a crash which occured when a resource with a precondition and/or a postcondition appeared inside a module with two or more instances. (#​31860)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[Siegrift]

Mhh, was this severe? How come we did not notice this?

[amarthadan]

Yes, it broke the deployment for GCP. It was caused by an incorrect merge. The OEV gateway was written in the old format but the format was updated before it was merged. And since it was a new part of the file it didn't create conflicts.

[Siegrift]

👍 LGTM, but haven't tested.