build(deps): update terraform hashicorp/terraform to v1.11.3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
hashicorp/terraform	required_version	minor	1.9.5 -> 1.11.3
hashicorp/terraform		minor	1.9.5 -> 1.11.3

---

Release Notes

hashicorp/terraform (hashicorp/terraform)

v1.11.3

Compare Source

1.11.3 (March 26, 2025)

BUG FIXES:

• Fixes unintended exit of CLI when using the remote backend and applying with post-plan tasks configured in HCP Terraform (#​36686)

• Modules with zero instances that contain ephemeral resources could produce an error during apply (#​36719)

v1.11.2

Compare Source

1.11.2 (March 12, 2025)

ENHANCEMENTS:

• Azure Backend supports ADO Pipelines OIDC token refresh by using the oidc_request_url, oidc_request_token and (the new) ado_pipeline_service_connection_id. (#​36458)

BUG FIXES:

• Return error when the templatestring function contains only a single interpolation that evaluates to a null value (#​36652)

• Backend/azure: subscription_id be optional & skip unnecessary management plane API call in some setup (#​36595)

NOTES:

• Updated dependency github.com/hashicorp/aws-sdk-go-base/v2 to v2.0.0-beta.62 to support newly added AWS regions (#​36625)

v1.11.1

Compare Source

1.11.1 (March 5, 2025)

BUG FIXES:

• Temporarily revert updated Windows symlink handling until we can account for known existing configurations using non-symlink junctions. (#​36575)

• terraform test: Fix crash when a run block attempts to cleanup after a non-applyable plan. (#​36582)

• Updated dependency golang.org/x/oauth2 from v0.23.0 => v0.27.0 to integrate latest changes (fix for CVE-2025-22868) (#​36584)

• lang/funcs/transpose: Avoid crash due to map with null values (#​36611)

• Combining ephemeral and sensitive marks could fail when serializing planned changes (#​36619)

v1.11.0

Compare Source

1.11.0 (February 27, 2025)

NEW FEATURES:

• Add write-only attributes to resources. Providers can specify that certain attributes are write-only. They are not persisted in state. You can use ephemeral values in write-only attributes. (#​36031)

• terraform test: The -junit-xml option for the terraform test command is now generally available. This option allows the command to create a test report in JUnit XML format. Feedback during the experimental phase helped map terraform test concepts to the JUnit XML format, and new additons may happen in future releases. (#​36324)

• S3 native state locking is now generally available. The use_lockfile argument enables users to adopt the S3-native mechanism for state locking. As part of this change, we've deprecated the DynamoDB-related arguments in favor of this new locking mechanism. While you can still use DynamoDB alongside S3-native state locking for migration purposes, we encourage migrating to the new state locking mechanism. (#​36338)

ENHANCEMENTS:

• init: Provider installation will utilise credentials configured in a .netrc file for the download and shasum URLs returned by provider registries. (#​35843)

• terraform test: Test runs now support using mocked or overridden values during unit test runs (e.g., with command = "plan"). Set override_during = plan in the test configuration to use the overridden values during the plan phase. The default value is override_during = apply. (#​36227)

• terraform test: Add new state_key attribute for run blocks, allowing test authors control over which internal state file should be used for the current test run. (#​36185)

• Updates the azure backend authentication to match the terraform-provider-azurermprovider authentication, in several ways:

  • github.com/hashicorp/go-azure-helpers: v0.43.0 -> v0.71.0
  • github.com/hashicorp/go-azure-sdk/[resource-manager/sdk]: v0.20241212.1154051. This replaces the deprecated Azure SDK used before
  • github.com/jackofallops/giovanni: v0.15.1 -> v0.27.0. Meanwhile, updating the azure storage API version from 2018-11-09 to 2023-11-03
  • Following new properties are added for the azure backend configuration:
    • use_cli
    • use_aks_workload_identity
    • client_id_file_path
    • client_certificate
    • client_id_file_path
    • client_secret_file_path
      (#​36258)

• Include ca-certificates package in our official Docker image to help with certificate handling by downstream (#​36486)

BUG FIXES:

• ephemeral values: correct error message when ephemeral values are included in provisioner output (#​36427)

• Attempting to override a variable during apply via TF_VAR_ environment variable will now yield warning instead of misleading error. (#​36435)

• backends: Fix crash when interrupting during interactive prompt for values (#​36448)

• Fixes hanging behavior seen when applying a saved plan with -auto-approve using the cloud backend (#​36453)

Previous Releases

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

• v1.10
• v1.9
• v1.8
• v1.7
• v1.6
• v1.5
• v1.4
• v1.3
• v1.2
• v1.1
• v1.0
• v0.15
• v0.14
• v0.13
• v0.12
• v0.11 and earlier

v1.10.5

Compare Source

1.10.5 (January 22, 2025)

BUG FIXES:

• element(...): no longer crashes when asked for a negative index into a tuple. (#​36376)

• Updated dependency github.com/hashicorp/go-slug v0.16.0 => v0.16.3 to integrate latest changes (fix for CVE-2025-0377) (#​36273)

• jsondecode(...): improved error message when objects contain duplicate keys (#​36376)

v1.10.4

Compare Source

1.10.4 (January 8, 2025)

BUG FIXES:

• type conversion: Empty map conversions now return correct type information (#​36262)

• terraform console: Fix crash when printing ephemeral values (#​36267)

v1.10.3

Compare Source

1.10.3 (December 18, 2024)

BUG FIXES:

• Terraform could panic when encountering an error during plan encoding (#​36212)

v1.10.2

Compare Source

1.10.2 (December 11, 2024)

BUG FIXES:

• cli: variables in an auto-loaded tfvars file which were overridden during plan incorrectly show as changed during apply [GH-36180]

v1.10.1

Compare Source

1.10.1 (December 4, 2024)

BUG FIXES:

• cli: Complex variables values set via environment variables were parsed incorrectly during apply (#​36121)
• config: templatefile would panic if given and entirely unknown map of variables (#​36118)
• config: templatefile would panic if the variables map contains marked values (#​36127)
• config: Remove constraint that an expanded resource block must only be used in conjunction with imports using for_each (#​36119)
• backend/s3: Lock files could not be written to buckets with object locking enabled (#​36120)

v1.10.0

Compare Source

1.10.0 (November 27, 2024)

NEW FEATURES:

• Ephemeral resources: Ephemeral resources are read anew during each phase of Terraform evaluation, and cannot be persisted to state storage. Ephemeral resources always produce ephemeral values.
• Ephemeral values: Input variables and outputs can now be defined as ephemeral. Ephemeral values may only be used in certain contexts in Terraform configuration, and are not persisted to the plan or state files.
  • ephemeralasnull function: a function takes a value of any type and returns a similar value of the same type with any ephemeral values replaced with non-ephemeral null values and all non-ephemeral values preserved.

BUG FIXES:

• The secret_suffix in the kubernetes backend now includes validation to prevent errors when the secret_suffix ends with a number (#​35666).
• The error message for an invalid default value for an input variable now indicates when the problem is with a nested value in a complex data type. (#​35465)
• Sensitive marks could be incorrectly transferred to nested resource values, causing erroneous changes during a plan (#​35501)
• Allow unknown error_message values to pass the core validate step, so variable validation can be completed later during plan
  (#​35537)
• Unencoded slashes within GitHub module source refs were being truncated and incorrectly used as subdirectories in the request path (#​35552)
• Terraform refresh-only plans with output only changes are now applyable. (#​35812)
• Postconditions referencing self with many instances could encounter an error during evaluation (#​35895)
• The plantimestamp() function would return an invalid date during validation (#​35902)
• Updates to resources which were forced to use create_before_destroy could lose that flag in the state temporarily and cause cycles if immediately removed from the configuration (#​35966)
• backend/cloud: Prefer KV tags, even when tags are defined as set (#​35937)
• Simplify config generation (plan -generate-config-out) for string attributes that contain primitive types (e.g. numbers or booleans) (#​35984)
• config: issensitive could incorrectly assert that an unknown value was not sensitive during plan, but later became sensitive during apply, causing failures where changes did not match the planned result (#​36012)
• config: The evaluation of conditional expressions and for expression in HCL could lose marks with certain combinations of unknown values (#​36017)

ENHANCEMENTS:

• The element function now accepts negative indices (#​35501)
• Import block validation has been improved to provide more useful errors and catch more invalid cases during terraform validate (#​35543)
• Performance enhancements for resource evaluation, especially when large numbers of resource instances are involved (#​35558)
• The plan, apply, and refresh commands now produce a deprecated warning when using the -state flag. Instead use the path attribute within the local backend to modify the state file. (#​35660)
• backend/cos: Add new auth for Tencent Cloud backend (#​35888)

UPGRADE NOTES:

• backend/s3: Removes deprecated attributes for assuming IAM role. Must use the assume_role block (#​35721)
• backend/s3: The s3 backend now supports S3 native state locking. When used with DynamoDB-based locking, locks will be acquired from both sources. In a future minor release of Terraform the DynamoDB locking mechanism and associated arguments will be deprecated. (#​35661)
• moved: Moved blocks now respect reserved keywords when parsing resource addresses. Configurations that reference resources with type names that match top level blocks and keywords from moved blocks will need to prepend the resource. identifier to these references. (#​35850)
• config: In order to ensure consistency in results from HCL conditional expressions, marks must be combined from all values within the expression to avoid losing mark information. This typically improves accuracy when validating configuration, but users may see sensitive results where they were lost previously.

Previous Releases

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

• v1.9
• v1.8
• v1.7
• v1.6
• v1.5
• v1.4
• v1.3
• v1.2
• v1.1
• v1.0
• v0.15
• v0.14
• v0.13
• v0.12
• v0.11 and earlier

v1.9.8

Compare Source

1.9.8 (October 16, 2024)

BUG FIXES:

• init: Highlight missing subdirectories of registry modules in error message (#​35848)
• init: Prevent crash when loading provider_meta blocks with invalid names (#​35842)
• config generation: Escape all invalid syntax in generate map keys with quotes (#​35837)
• plan: also validate provider requirements from state (#​35864)

v1.9.7

Compare Source

1.9.7 (October 2, 2024)

BUG FIXES:

• config generation: escape map keys with whitespaces (#​35754)

v1.9.6

Compare Source

1.9.6 (September 18, 2024)

BUG FIXES:

• plan renderer: Render complete changes within unknown nested blocks. (#​35644)
• plan renderer: Fix crash when attempting to render unknown nested blocks that contain attributes forcing resource replacement. (#​35644)
• plan renderer: Fix crash when rendering a plan that contains null attributes being update to unknown values. (#​35709)

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

🖌 Terraform Format and Style ✅

⚙️ Terraform Initialization ✅

🤖 Terraform Validation ✅

Validation Output

🦙 Terraform Lint ✅

Lint Output

📖 Terraform Plan ❌

Show Plan

Running plan in HCP Terraform. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

The remote workspace is configured to work with configuration at
scaleway relative to the target repository.

Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/demo-infrastructure/demo-infrastructure/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
    /home/runner/work/demo-infrastructure/demo-infrastructure

To view this run in a browser, visit:
https://app.terraform.io/app/parca-dev/demo-infrastructure-scaleway/runs/run-D9EEXaaEeYdChoMh

Waiting for the plan to start...

Terraform v1.9.5
on linux_amd64
Initializing plugins and modules...
�[0m�[1mInitializing HCP Terraform...�[0m
�[31m╷�[0m�[0m
�[31m│�[0m �[0m�[1m�[31mError: �[0m�[0m�[1mUnsupported Terraform Core version�[0m
�[31m│�[0m �[0m
�[31m│�[0m �[0m�[0m  on versions.tf line 2, in terraform:
�[31m│�[0m �[0m   2:   �[4mrequired_version = "1.11.3"�[0m�[0m
�[31m│�[0m �[0m
�[31m│�[0m �[0mThis configuration does not support Terraform version 1.9.5. To proceed,
�[31m│�[0m �[0meither choose another supported Terraform version or update this version
�[31m│�[0m �[0mconstraint. Version constraints are normally set for good reason, so
�[31m│�[0m �[0mupdating the constraint may lead to other errors or unexpected behavior.
�[31m╵�[0m�[0m
Operation failed: failed running terraform init (exit 1)

Pusher: @renovate[bot], Action: pull_request, Working Directory: scaleway, Workflow: Terraform