Update dependency hashicorp/terraform to v1.14.3

[renovate]

This PR contains the following updates:

Package	Update	Change
hashicorp/terraform	minor	1.13.3 → 1.14.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

hashicorp/terraform (hashicorp/terraform)

v1.14.3

Compare Source

1.14.3 (December 17, 2025)

BUG FIXES:

• stacks: change absolute paths in path.module/path.root to be relative, as documented (#​37982)

v1.14.2

Compare Source

v1.14.1

Compare Source

1.14.1 (December 3, 2025)

BUG FIXES:

• test: allow ephemeral outputs in root modules (#​37813)

• Combinations of replace_triggered_by and -replace could result in some instances not being replaced (#​37833)

• providers lock: include providers required by terraform test (#​37851)

• Set state information in the proto request for the GenerateResourceConfig RPC (#​37896)

• actions: make after_create & after_update actions run after the resource has applied (#​37936)

v1.14.0

Compare Source

1.14.0 (November 19, 2025)

NEW FEATURES:

• List Resources: List resources can be defined in *.tfquery.hcl files and allow querying and filterting existing infrastructure.

• A new Terraform command terraform query: Executes list operations against existing infrastructure and displays the results. The command can optionally generate configuration for importing results into Terraform.

• A new GenerateResourceConfiguration RPC allows providers to create more precise configuration values during import. (#​37515)

• New top-level Actions block: Actions are provider defined and meant to codify use cases outside the normal CRUD model in your Terraform configuration. Providers can define Actions like aws_lambda_invoke or aws_cloudfront_create_invalidation that do something imparative outside of Terraforms normal CRUD model. You can configure such a side-effect with an action block and have actions triggered through the lifecycle of a resource or through passing the -invoke CLI flag. (#​37553)

ENHANCEMENTS:

• terraform test: expected diagnostics will be included in test output when running in verbose mode" (#​37362)

• terraform test: ignore prevent_destroy attribute during when cleaning up tests" (#​37364)

• terraform stacks command support for -help flag (#​37645)

• query: support offline validation of query files via -query flag in the validate command (#​37671)

• Updates to support the AWS European Sovereign Cloud (#​37721)

BUG FIXES:

• Retrieve all workspace variables while doing a terraform import, include variables inherited from variable sets but not overwritten by the workspace. (#​37241)

• Fix OSS backend proxy support by adding a proxy layer for OSS backend operations. Resolves #​36897. (#​36897)

• console and test: return explicit diagnostics when referencing resources that were not included in the most recent operation. (#​37663)

• query: generate unique resource identifiers for results of expanded list resources (#​37681)

• The CLI now summarizes the number of actions invoked during terraform apply, matching the plan output. (#​37689)

• Allow filesystem functions to return inconsistent results when evaluated within provider configuration (#​37854)

• query: improve error handling for missing identity schemas (#​37863)

UPGRADE NOTES:

• The parallelism of Terraform operations within container runtimes may be reduced depending on the CPU bandwidth limit setting. (#​37436)

• Building Terraform 1.14 requires macOS Monterey or later (due to being built on Go 1.25 which imposes these requirements) (#​37436)

Previous Releases

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

• v1.13
• v1.12
• v1.11
• 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.13.5

Compare Source

1.13.5 (November 5, 2025)

BUG FIXES:

• impure functions could cause templatefile to incorrectly fail consistency checks (#​37807)

• Allow filesystem functions to return inconsistent results when evaluated within provider configuration (#​37854)

v1.13.4

Compare Source

1.13.4 (October 15, 2025)

BUG FIXES:

• Fix crash when showing a cloud plan without having a cloud backend (#​37751)

---

Configuration

📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 this update again.

---

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

---

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

[hmcts-jenkins-j-to-z]

Plan Result (aat)

Plan: 0 to add, 1 to change, 0 to destroy.

• Update
  • module.redis-cache.azurerm_redis_cache.redis

Change Result (Click me)

  # module.redis-cache.azurerm_redis_cache.redis will be updated in-place
  ~ resource "azurerm_redis_cache" "redis" {
        id                                 = "/subscriptions/1c4f0704-a29e-403d-b719-b90c34ef14c9/resourceGroups/sscs-cache-aat/providers/Microsoft.Cache/redis/sscs-aat"
        name                               = "sscs-aat"
        tags                               = {
            "application"         = "social-service-child-support"
            "autoShutdown"        = "true"
            "builtFrom"           = "https://github.com/HMCTS/sscs-submit-your-appeal.git"
            "businessArea"        = "CFT"
            "contactSlackChannel" = "#sscs-tech"
            "environment"         = "staging"
            "managedBy"           = "SSCS"
        }
        # (24 unchanged attributes hidden)

      ~ redis_configuration {
          ~ maxfragmentationmemory_reserved         = 125 -> 642
          ~ maxmemory_delta                         = 125 -> 642
          ~ maxmemory_reserved                      = 125 -> 642
            # (14 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

[hmcts-jenkins-j-to-z]

Plan Result (prod)

No changes. Your infrastructure matches the configuration.

[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.