Update dependency hashicorp/terraform to v1.11.4 #659

renovate · 2024-11-21T09:27:45Z

This PR contains the following updates:

Package	Update	Change
hashicorp/terraform	minor	`1.4.0` -> `1.11.4`

Release Notes

hashicorp/terraform (hashicorp/terraform)

`v1.11.4`

Compare Source

1.11.4 (April 9, 2025)

BUG FIXES:

disable X25519Kyber768Draft00 in TLS to prevent timouts with some AWS network firewalls (#36791)
write-only attributes: internal providers should set write-only attributes to null (#36824)

`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.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.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)

`v1.9.5`

Compare Source

1.9.5 (August 20, 2024)

ENHANCEMENTS:

cloud: The cloud block can now interact with workspaces that have HCP resource IDs. (#35495)

BUG FIXES:

core: removed blocks with provisioners were not executed when the resource was in a nested module. (#35611)

`v1.9.4`

Compare Source

1.9.4 (August 7, 2024)

BUG FIXES:

core: Unneeded variable validations were being executed during a destroy plan, which could cause plans starting with incomplete state to fail. (#35511)
init: Don't crash when discovering invalid syntax in duplicate required_providers blocks. (#35533)

`v1.9.3`

Compare Source

1.9.3 (July 24, 2024)

ENHANCEMENTS:

Terraform now returns a more specific error message in the awkward situation where an input variable validation rule is known to have failed (condition returned false) but the error message is derived from an unknown value. (#35400)

BUG FIXES:

core: Terraform no longer performs an unnecessary refresh when removing an instance targeted by a removed block. (#35458)
config generation: Fix validation error when using nested computed or deprecated attributes. (#35484)
Updated to newer github.com/hashicorp/go-retryablehttp version, addressing CVE-2024-6104, and bringing in updates for several indirect dependencies. (#35473)
Moved to building with Go 1.22.5, which addresses CVE-2024-24791 and several other non-security bugs. (#35494)

`v1.9.2`

Compare Source

1.9.2 (July 10, 2024)

BUG FIXES:

core: Fix panic when self-referencing direct instances from count and for_each meta attributes. (#35432)

`v1.9.1`

Compare Source

1.9.1 (July 3, 2024)

UPGRADE NOTES:

Library used by Terraform (hashicorp/go-getter) for installing/updating modules was upgraded from v1.7.4 to v1.7.5. This addresses CVE-2024-6257. This change may have a negative effect on performance of terraform init or terraform get in case of larger git repositories. Please do file an issue if you find the performance difference noticable. (#35376)

BUG FIXES:

terraform test: Removed additional erroneous error message when referencing attributes that don't exist. (#35408)
import blocks: Fix crash that occurs when incorrectly referencing the to resource from the id attribute. (#35420)

`v1.9.0`

Compare Source

1.9.0 (June 26, 2024)

If you are upgrading from an earlier minor release, please refer to the Terraform v1.9 Upgrade Guide.

NEW FEATURES:

Input variable validation rules can refer to other objects: Previously input variable validation rules could refer only to the variable being validated. Now they are general expressions, similar to those elsewhere in a module, which can refer to other input variables and to other objects such as data resources.
templatestring function: a new built-in function which is similar to templatefile but designed to render templates obtained dynamically, such as from a data resource result.

ENHANCEMENTS:

terraform plan: Improved presentation of OPA and Sentinel policy evaluations in HCP Terraform remote runs, for logical separation.
terraform init now accepts a -json option. If specified, enables the machine readable JSON output. (#34886)
terraform test: Test runs can now pass sensitive values to input variables while preserving their dynamic sensitivity. Previously sensitivity would be preserved only for variables statically declared as being sensitive, using sensitive = true. (#35021)
config: Input variable validation rules can now refer to other objects in the same module. (#34955)
config: templatestring function allows rendering a template provided as a string. (#34968, #35224, #35285)
core: Performance improvement during graph building for configurations with an extremely large number of resource blocks. (#35088)
built-in terraform provider: Allows moved block refactoring from the hashicorp/null provider null_resource resource type to the terraform_data resource type. (#35163)
terraform output with cloud block: Terraform no longer suggests that data loss could occur when outputs are not available. (#35143)
terraform console: Now has basic support for multi-line input in interactive mode. (#34822)
If an entered line contains opening parentheses/etc that are not closed, Terraform will await another line of input to complete the expression. This initial implementation is primarily intended to support pasting in multi-line expressions from elsewhere, rather than for manual multi-line editing, so the interactive editing support is currently limited.
cli: Reduced copying of state to improve performance with large numbers of resources. (#35164)
removed blocks can now declare destroy-time provisioners which will be executed when the associated resource instances are destroyed. (#35230)

BUG FIXES:

remote-exec provisioner: Each remote connection will now be closed immediately after use. (#34137)
backend/s3: Fixed the digest value displayed for DynamoDB/S3 state checksum mismatches. (#34387)
terraform test: Fix bug in which non-Hashicorp providers required by testing modules and initialised within the test files were assigned incorrect registry addresses. (#35161)
config: The templatefile function no longer returns a "panic" error if the template file path is marked as sensitive. Instead, the template rendering result is also marked as sensitive. (#35180)
config: import blocks which referenced resources in non-existent modules were silently ignored when they should have raised an error (#35330)
terraform init: When selecting a version for a provider that has both positive and negative version constraints for the same prerelease -- e.g. 1.2.0-beta.1, !1.2.0-beta.1 -- the negative constraint will now overrule the positive, for consistency with how negative constraints are handled otherwise. Previously Terraform would incorrectly treat the positive as overriding the negative if the specified version was a prerelease. (#35181)
import: import blocks could block a destroy operation if the target resource was already deleted (#35272)
cli: plan output was missing blocks which were entirely unknown (#35271)
cli: fix crash when running providers mirror with an incomplete lock file (#35322)
core: Changing create_before_destroy when replacing an instance, then applying with -refresh=false would order the apply operations incorrectly (#35261)
core: Resource addresses that start with the optional resource. prefix will now be correctly parsed when used as an address target. (#35333)

UPGRADE NOTES:

terraform test: It is no longer valid to specify version constraints within provider blocks within .tftest.hcl files. Instead, version constraints must be supplied within the main configuration where the provider is in use.
import: Invalid import blocks pointing to nonexistent modules were mistakenly ignored in prior versions. These will need to be fixed or removed in v1.9.

Previous Releases

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

`v1.8.5`

Compare Source

1.8.5 (June 5, 2024)

BUG FIXES:

terraform test: Remove duplicate warning diagnostic when providing values for unknown variables in run blocks. (#35172)

`v1.8.4`

Compare Source

1.8.4 (May 22, 2024)

BUG FIXES:

core: Fix exponential slowdown in some cases when modules are using depends_on. (#35157)
import blocks: Fix bug where resources with nested, computed, and optional id attributes would fail to generate configuration. (#35220)
Updated to new golang.org/x/net release, which addressed CVE-2023-45288 (#35165)

`v1.8.3`

Compare Source

1.8.3 (May 8, 2024)

BUG FIXES:

terraform test: Providers configured within an overridden module could panic. (#35110)
core: Fix crash when a provider incorrectly plans a nested object when the configuration is null (#35090)

`v1.8.2`

Compare Source

1.8.2 (April 24, 2024)

BUG FIXES:

terraform apply: Prevent panic when a provider erroneously provides unknown values. (#35048)
terraform plan: Replace panic with error message when self-referencing resources and data sources from the count and for_each meta attributes. (#35047)
terraform test: Restore TF_ENV_* variables being made available to testing modules. (#35014)
terraform test: Prevent crash when referencing local variables within overridden modules. (#35030)

ENHANCEMENTS:

Improved performance by removing unneeded additional computation for a disabled experimental feature. (#35066)

OTHER CHANGES:

Update all references to Terraform Cloud to refer to HCP Terraform, the service's new name. This only affects display text; the cloud block and environment variables like TF_CLOUD_ORGANIZATION remain unchanged. (#35050)

NOTE:

Starting with this release, we are including a copy of our license file in all packaged versions of our releases, such as the release .zip files. If you are consuming these files directly and would prefer to extract the one terraform file instead of extracting everything, you need to add an extra argument specifying the file to extract, like this:

unzip terraform_1.8.2_linux_amd64.zip terraform

`v1.8.1`

Compare Source

1.8.1 (April 17, 2024)

BUG FIXES:

Fix crash in terraform plan when referencing a module output that does not exist within the try(...) function. (#34985)
Fix crash in terraform apply when referencing a module with no planned changes. (#34985)
moved block: Fix crash when move targets a module which no longer exists. (#34986)
import block: Fix crash when generating configuration for resources with complex sensitive attributes. (#34996)
Plan renderer: Correctly render strings that begin with JSON compatible text but don't end with it. (#34959)

`v1.8.0`

Compare Source

1.8.0 (April 10, 2024)

If you are upgrading from Terraform v1.7 or earlier, please refer to
the Terraform v1.8 Upgrade Guide.

NEW FEATURES:

Providers can now offer functions which can be used from within the Terraform configuration language.

The syntax for calling a provider-contributed function is provider::provider_name::function_name(). (#34394)
Providers can now transfer the ownership of a remote object between resources of different types, for situations where there are two different resource types that represent the same remote object type.

This extends the moved block behavior to support moving between two resources of different types only if the provider for the target resource type declares that it can convert from the source resource type. Refer to provider documentation for details on which pairs of resource types are supported.
New issensitive function returns true if the given value is marked as sensitive.

ENHANCEMENTS:

terraform test: File-level variables can now refer to global variables. (#34699)
When generating configuration based on import blocks, Terraform will detect strings that contain valid JSON syntax and generate them as calls to the jsonencode function, rather than generating a single string. This is primarily motivated by readability, but might also be useful if you need to replace part of the literal value with an expression as you generalize your module beyond the one example used for importing.
terraform plan now uses a different presentation for describing changes to lists where the old and new lists have the same length. It now compares the elements with correlated indices and shows a separate diff for each one, rather than trying to show a diff for the list as a whole. The behavior is unchanged for lists of different lengths.
terraform providers lock accepts a new boolean option -enable-plugin-cache. If specified, and if a global plugin cache is configured, Terraform will use the cache in the provider lock process. (#34632)
built-in "terraform" provider: new decode_tfvars, encode_tfvars, and encode_expr functions, for unusual situations where it's helpful to manually generate or read from Terraform's "tfvars" format. (#34718)
terraform show's JSON rendering of a plan now includes two explicit flags "applyable" and "complete", which both summarize characteristics of a plan that were previously only inferrable by consumers replicating some of Terraform Core's own logic. (#34642)

"applyable" means that it makes sense for a wrapping automation to offer to apply this plan.

"complete" means that applying this plan is expected to achieve convergence between desired and actual state. If this flag is present and set to false then wrapping automations should ideally encourage an operator to run another plan/apply round to continue making progress toward convergence.

BUG FIXES:

core: Sensitive values will now be tracked more accurately in state and plans, preventing unexpected updates with no apparent changes. (#34567)
core: Fix incorrect error message when using in invalid iterator argument within a dynamic block. (#34751)
core: Fixed edge-case bug that could cause loss of floating point precision when round-tripping due to incorrectly using a MessagePack integer to represent a large non-integral number. (#24576)
config: Converting from an unknown map value to an object type now correctly handles the situation where the map element type disagrees with an optional attribute of the target type, since when a map value is unknown we don't yet know which keys it has and thus cannot predict what subset of the elements will get converted as attributes in the resulting object. (#34756)
cloud: Fixed unparsed color codes in policy failure error messages. (#34473)

Previous Releases

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

`v1.7.5`

Compare Source

1.7.5 (March 13, 2024)

BUG FIXES:

backend/s3: When using s3 backend and encountering a network issue, the retry code would fail with "failed to rewind transport stream for retry". Now the retry should be successful. (#34796)

`v1.7.4`

Compare Source

1.7.4 (February 21, 2024)

BUG FIXES:

terraform test: Fix automatic loading of variable files within the test directory on windows platforms. (#34666)
plan renderer: Very large numbers (> 2^63) will no longer be truncated in the human-readable plan. (#34702)

`v1.7.3`

Compare Source

1.7.3 (February 7, 2024)

BUG FIXES:

terraform test: Fix crash when dynamic-typed attributes are not assigned values in mocks. (#34610)
provisioners/file: Fix panic when source is null. (#34621)
import: Throw helpful error message if an import block is configured with an empty ID (34625)

`v1.7.2`

Compare Source

1.7.2 (January 31, 2024)

BUG FIXES:

backend/s3: No longer returns error when IAM user or role does not have access to the default workspace prefix env:. (#34511)
cloud: When triggering a run, the .terraform/modules directory was being excluded from the configuration upload causing Terraform Cloud to try (and sometimes fail) to re-download the modules. (#34543)

ENHANCEMENTS:

terraform fmt: Terraform mock data files (.tfmock.hcl) will now be included when executing the format command. (#34580)
Add additional diagnostics when a generated provider block that fails schema validation requires explicit configuration. (#34595)

`v1.7.1`

Compare Source

1.7.1 (January 24, 2024)

BUG FIXES:

terraform test: Fix crash when referencing variables or functions within the file level variables block. (#34531)
terraform test: Fix crash when override_module block was missing the outputs attribute. (#34563)

`v1.7.0`

Compare Source

1.7.0 (January 17, 2024)

UPGRADE NOTES:

Input validations are being restored to the state file in this version of Terraform. Due to a state interoperability issue (#33770) in earlier versions, users that require interaction between different minor series should ensure they have upgraded to the following patches:
- Users of Terraform prior to 1.3.0 are unaffected;
- Terraform 1.3 series users should upgrade to 1.3.10;
- Terraform 1.4 series users should upgrade to 1.4.7;
- Terraform 1.5 series users should upgrade to 1.5.7;
- Users of Terraform 1.6.0 and later are unaffected.
  This is important for users with terraform_remote_state data sources reading remote state across different versions of Terraform.
nonsensitive function no longer raises an error when applied to a value that is already non-sensitive. (#33856)
terraform graph now produces a simplified graph describing only relationships between resources by default, for consistency with the granularity of information returned by other commands that emphasize resources as the main interesting object type and de-emphasize the other "glue" objects that connect them.

The type of graph that earlier versions of Terraform produced by default is still available with explicit use of the -type=plan option, producing an approximation of the real dependency graph Terraform Core would use to construct a plan.
terraform test: Simplify the ordering of destroy operations during test cleanup to simple reverse run block order. (#34293)
backend/s3: The use_legacy_workflow argument now defaults to false. The backend will now search for credentials in the same order as the default provider chain in the AWS SDKs and AWS CLI. To revert to the legacy credential provider chain ordering, set this value to true. This argument, and the ability to use the legacy workflow, is deprecated. To encourage consistency with the AWS SDKs, this argument will be removed in a future minor version.

NEW FEATURES:

terraform test: Providers, modules, resources, and data sources can now be mocked during executions of terraform test. The following new blocks have been introduced within .tftest.hcl files:
- mock_provider: Can replace provider instances with mocked providers, allowing tests to execute in command = apply mode without requiring a configured cloud provider account and credentials. Terraform will create fake resources for mocked providers and maintain them in state for the lifecycle of the given test file.
- override_resource: Specific resources can be overridden so Terraform will create a fake resource with custom values instead of creating infrastructure for the overridden resource.
- override_data: Specific data sources can be overridden so data can be imported into tests without requiring real infrastructure to be created externally first.
- override_module: Specific modules can be overridden in their entirety to give greater control over the returned outputs without requiring in-depth knowledge of the module itself.
removed block for refactoring modules: Module authors can now record in source code when a resource or module call has been removed from configuration, and can inform Terraform whether the corresponding object should be deleted or simply removed from state.

This effectively provides a configuration-driven workflow to replace terraform state rm. Removing an object from state is a new type of action which is planned and applied like any other. The terraform state rm command will remain available for scenarios in which directly modifying the state file is appropriate.

BUG FIXES:

Ignore potential remote terraform version mismatch when running force-unlock (#28853)
Exit Dockerfile build script early on cd failure. (#34128)
terraform test: Stop attempting to destroy run blocks that have no actual infrastructure to destroy. This fixes an issue where attempts to destroy "verification" run blocks that load only data sources would fail if the underlying infrastructure referenced by the run blocks had already been destroyed. (#34331)
terraform test: Improve error message for invalid run block names. (#34469)
terraform test: Fix bug where outputs in "empty" modules were not available to the assertions from Terraform test files. (#34482)
security: Upstream patch to mitigate the security advisory CVE-2023-48795, which potentially affects local-exec and file provisioners connecting to remote hosts using SSH. (#34426)

ENHANCEMENTS:

terraform test: Providers defined within test files can now reference variables from their configuration that are defined within the test file. (#34069)
terraform test: Providers defined within test files can now reference outputs from run blocks. (#34118)
terraform test: Terraform functions are now available within variables and provider blocks within test files. (#34204)
terraform test: Terraform will now load variables from any terraform.tfvars within the testing directory, and apply the variable values to tests within the same directory. (#34341)
terraform graph: Now produces a simplified resources-only graph by default. (#34288)
terraform console: Now supports a -plan option which allows evaluating expressions against the planned new state, rather than against the prior state. This provides a more complete set of values for use in console expressions, at the expense of a slower startup time due first calculating the plan. (#34342)
import: for_each can now be used to expand the import block to handle multiple resource instances (#33932)
If the proposed change for a resource instance is rejected either due to a postcondition block or a prevent_destroy setting, Terraform will now include that proposed change in the plan output alongside the relevant error, whereas before the error would replace the proposed change in the output. (#34312)
.terraformignore: improve performance when ignoring large directories (#34400)

Previous Releases

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

`v1.6.6`

Compare Source

1.6.6 (December 13, 2023)

BUG FIXES:

terraform test: Stop attempting to destroy run blocks that have no actual infrastructure to destroy. This fixes an issue where attempts to destroy "verification" run blocks that load only data sources would fail if the underlying infrastructure referenced by the run blocks had already been destroyed. (#34331)
cloud: prevent running saved cloud plans in VCS-connected workspaces. Saved plans might be applied later, and VCS workspaces shouldn't apply configurations that don't come from their designated VCS branch.
core: Unmanaged plugins (mainly used by provider acceptance testing) would not have a provider address set, preventing the caching of their schemas (#34380)

`v1.6.5`

Compare Source

1.6.5 (November 29, 2023)

BUG FIXES:

backend/s3: Fixes parsing errors in shared config and credentials files. (#34313)
backend/s3: Fixes error with AWS SSO when using FIPS endpoints. (#34313)

`v1.6.4`

Compare Source

1.6.4 (November 15, 2023)

ENHANCEMENTS:

backend/s3: Add the parameter endpoints.sso to allow overriding the AWS SSO API endpoint. (#34195)

BUG FIXES:

terraform test: Fix bug preventing passing sensitive output values from previous run blocks as inputs to future run blocks. (#34190)
backend/s3: Add https_proxy and no_proxy parameters to allow fully specifying proxy configuration (#34243)

`v1.6.3`

Compare Source

1.6.3 (November 1, 2023)

ENHANCEMENTS:

backend/s3: Adds the parameter skip_s3_checksum to allow users to disable checksum on S3 uploads for compatibility with "S3-compatible"

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-a-to-c · 2024-11-21T09:35:35Z

Plan Result (aat)

⚠️ Resource Deletion will happen

This plan contains resource delete operation. Please check the plan result very carefully!

Plan: 3 to add, 0 to change, 2 to destroy.

Create
- module.bar-database-v15.azurerm_postgresql_flexible_server_active_directory_administrator.pgsql_adadmin
Replace
- module.sdp_db_user[0].azurerm_key_vault_secret.sdp_vault_sdp_read_user_name
- module.sdp_db_user[0].azurerm_key_vault_secret.sdp_vault_sdp_read_user_password

Change Result (Click me)

  # module.bar-database-v15.azurerm_postgresql_flexible_server_active_directory_administrator.pgsql_adadmin will be created
  + resource "azurerm_postgresql_flexible_server_active_directory_administrator" "pgsql_adadmin" {
      + id                  = (known after apply)
      + object_id           = "e7ea2042-4ced-45dd-8ae3-e051c6551789"
      + principal_name      = "DTS Platform Operations"
      + principal_type      = "Group"
      + resource_group_name = "bar-postgres-db-v15-data-aat"
      + server_name         = "bar-postgres-db-v15-aat"
      + tenant_id           = "531ff96d-0ae9-462a-8d2d-bec7c0b42082"
    }

  # module.sdp_db_user[0].data.azurerm_key_vault.sdp_vault will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "azurerm_key_vault" "sdp_vault" {
      + access_policy                   = (known after apply)
      + enable_rbac_authorization       = (known after apply)
      + enabled_for_deployment          = (known after apply)
      + enabled_for_disk_encryption     = (known after apply)
      + enabled_for_template_deployment = (known after apply)
      + id                              = (known after apply)
      + location                        = (known after apply)
      + name                            = "mi-vault-dev"
      + network_acls                    = (known after apply)
      + public_network_access_enabled   = (known after apply)
      + purge_protection_enabled        = (known after apply)
      + resource_group_name             = "mi-dev-rg"
      + sku_name                        = (known after apply)
      + tags                            = (known after apply)
      + tenant_id                       = (known after apply)
      + vault_uri                       = (known after apply)
    }

  # module.sdp_db_user[0].data.azurerm_subscription.current will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "azurerm_subscription" "current" {
      + display_name          = (known after apply)
      + id                    = (known after apply)
      + location_placement_id = (known after apply)
      + quota_id              = (known after apply)
      + spending_limit        = (known after apply)
      + state                 = (known after apply)
      + subscription_id       = (known after apply)
      + tags                  = (known after apply)
      + tenant_id             = (known after apply)
    }

  # module.sdp_db_user[0].azurerm_key_vault_secret.sdp_vault_sdp_read_user_name must be replaced
-/+ resource "azurerm_key_vault_secret" "sdp_vault_sdp_read_user_name" {
      ~ id                      = "https://mi-vault-dev.vault.azure.net/secrets/bar-postgres-db-v15-aat-read-user-name/610b672596634dd4a4542cf5e3dda865" -> (known after apply)
      ~ key_vault_id            = "/subscriptions/867a878b-cb68-4de5-9741-361ac9e178b6/resourceGroups/mi-dev-rg/providers/Microsoft.KeyVault/vaults/mi-vault-dev" -> (known after apply) # forces replacement
        name                    = "bar-postgres-db-v15-aat-read-user-name"
      ~ resource_id             = "/subscriptions/867a878b-cb68-4de5-9741-361ac9e178b6/resourceGroups/mi-dev-rg/providers/Microsoft.KeyVault/vaults/mi-vault-dev/secrets/bar-postgres-db-v15-aat-read-user-name/versions/610b672596634dd4a4542cf5e3dda865" -> (known after apply)
      ~ resource_versionless_id = "/subscriptions/867a878b-cb68-4de5-9741-361ac9e178b6/resourceGroups/mi-dev-rg/providers/Microsoft.KeyVault/vaults/mi-vault-dev/secrets/bar-postgres-db-v15-aat-read-user-name" -> (known after apply)
      - tags                    = {} -> null
      - value_wo_version        = 0 -> null
      ~ version                 = "610b672596634dd4a4542cf5e3dda865" -> (known after apply)
      ~ versionless_id          = "https://mi-vault-dev.vault.azure.net/secrets/bar-postgres-db-v15-aat-read-user-name" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

  # module.sdp_db_user[0].azurerm_key_vault_secret.sdp_vault_sdp_read_user_password must be replaced
-/+ resource "azurerm_key_vault_secret" "sdp_vault_sdp_read_user_password" {
      ~ id                      = "https://mi-vault-dev.vault.azure.net/secrets/bar-postgres-db-v15-aat-read-user-password/484bdc03c87140a282b21f645e98b4de" -> (known after apply)
      ~ key_vault_id            = "/subscriptions/867a878b-cb68-4de5-9741-361ac9e178b6/resourceGroups/mi-dev-rg/providers/Microsoft.KeyVault/vaults/mi-vault-dev" -> (known after apply) # forces replacement
        name                    = "bar-postgres-db-v15-aat-read-user-password"
      ~ resource_id             = "/subscriptions/867a878b-cb68-4de5-9741-361ac9e178b6/resourceGroups/mi-dev-rg/providers/Microsoft.KeyVault/vaults/mi-vault-dev/secrets/bar-postgres-db-v15-aat-read-user-password/versions/484bdc03c87140a282b21f645e98b4de" -> (known after apply)
      ~ resource_versionless_id = "/subscriptions/867a878b-cb68-4de5-9741-361ac9e178b6/resourceGroups/mi-dev-rg/providers/Microsoft.KeyVault/vaults/mi-vault-dev/secrets/bar-postgres-db-v15-aat-read-user-password" -> (known after apply)
      - tags                    = {} -> null
      - value_wo_version        = 0 -> null
      ~ version                 = "484bdc03c87140a282b21f645e98b4de" -> (known after apply)
      ~ versionless_id          = "https://mi-vault-dev.vault.azure.net/secrets/bar-postgres-db-v15-aat-read-user-password" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

Plan: 3 to add, 0 to change, 2 to destroy.

hmcts-jenkins-a-to-c · 2024-11-21T09:36:16Z

Plan Result (prod)

No changes. Your infrastructure matches the configuration.

renovate · 2025-04-11T15:03:19Z

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (1.11.4). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

renovate bot added the dependencies Pull requests that update a dependency file label Nov 21, 2024

renovate-approve bot approved these changes Nov 21, 2024

View reviewed changes

renovate-approve-2 bot approved these changes Nov 21, 2024

View reviewed changes

hmcts-jenkins-a-to-c bot added the aat/destroy label Nov 21, 2024

hmcts-jenkins-a-to-c bot added the prod/destroy label Nov 21, 2024

hmcts-jenkins-a-to-c bot deployed to preview November 21, 2024 09:36 View deployment

hmcts-jenkins-a-to-c bot added ns:bar prd:bar rel:bar-api-pr-659 labels Nov 21, 2024

renovate bot force-pushed the renovate/terraform-monorepo branch from 738f4fb to 9dc3088 Compare November 27, 2024 14:53

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.9.8~~ Update dependency hashicorp/terraform to v1.10.0 Nov 27, 2024

hmcts-jenkins-a-to-c bot deployed to preview November 27, 2024 15:00 View deployment

renovate bot force-pushed the renovate/terraform-monorepo branch from 9dc3088 to 118d368 Compare December 5, 2024 23:47

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.10.0~~ Update dependency hashicorp/terraform to v1.10.1 Dec 5, 2024

renovate bot force-pushed the renovate/terraform-monorepo branch from 118d368 to 40db87e Compare December 11, 2024 17:38

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.10.1~~ Update dependency hashicorp/terraform to v1.10.2 Dec 11, 2024

hmcts-jenkins-a-to-c bot deployed to preview December 11, 2024 17:44 View deployment

renovate bot force-pushed the renovate/terraform-monorepo branch from 40db87e to c0dc96c Compare December 20, 2024 05:55

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.10.2~~ Update dependency hashicorp/terraform to v1.10.3 Dec 20, 2024

hmcts-jenkins-a-to-c bot deployed to preview December 20, 2024 07:32 View deployment

renovate bot force-pushed the renovate/terraform-monorepo branch from c0dc96c to fda2819 Compare January 9, 2025 03:59

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.10.3~~ Update dependency hashicorp/terraform to v1.10.4 Jan 9, 2025

renovate bot force-pushed the renovate/terraform-monorepo branch from fda2819 to 92aefbe Compare January 17, 2025 10:28

hmcts-jenkins-a-to-c bot removed the aat/destroy label Jan 17, 2025

hmcts-jenkins-a-to-c bot deployed to preview January 17, 2025 10:37 View deployment

renovate bot force-pushed the renovate/terraform-monorepo branch from 92aefbe to 973004f Compare January 17, 2025 16:15

hmcts-jenkins-a-to-c bot removed the prod/destroy label Jan 17, 2025

hmcts-jenkins-a-to-c bot deployed to preview January 17, 2025 16:25 View deployment

renovate bot force-pushed the renovate/terraform-monorepo branch from 973004f to 41aaa7d Compare January 24, 2025 07:51

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.10.4~~ Update dependency hashicorp/terraform to v1.10.5 Jan 24, 2025

hmcts-jenkins-a-to-c bot deployed to preview January 24, 2025 07:59 View deployment

renovate bot force-pushed the renovate/terraform-monorepo branch from 41aaa7d to cdbc4ff Compare January 27, 2025 16:02

hmcts-jenkins-a-to-c bot deployed to preview January 27, 2025 16:11 View deployment

renovate bot force-pushed the renovate/terraform-monorepo branch from cdbc4ff to f789b0c Compare February 28, 2025 23:49

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.10.5~~ Update dependency hashicorp/terraform to v1.11.0 Feb 28, 2025

renovate bot force-pushed the renovate/terraform-monorepo branch from f789b0c to 81301c8 Compare March 5, 2025 20:09

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.11.0~~ Update dependency hashicorp/terraform to v1.11.1 Mar 5, 2025

hmcts-jenkins-a-to-c bot added aat/no-changes prod/no-changes labels Mar 6, 2025

hmcts-jenkins-a-to-c bot requested a deployment to preview March 6, 2025 07:15 Abandoned

renovate bot force-pushed the renovate/terraform-monorepo branch from 81301c8 to 30872d9 Compare March 13, 2025 12:20

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.11.1~~ Update dependency hashicorp/terraform to v1.11.2 Mar 13, 2025

hmcts-jenkins-a-to-c bot requested a deployment to preview March 13, 2025 12:27 Abandoned

renovate bot force-pushed the renovate/terraform-monorepo branch from 30872d9 to ee8494b Compare March 28, 2025 23:56

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.11.2~~ Update dependency hashicorp/terraform to v1.11.3 Mar 28, 2025

hmcts-jenkins-a-to-c bot requested a deployment to preview March 31, 2025 06:59 Abandoned

Update dependency hashicorp/terraform to v1.11.4

55d26ed

renovate bot force-pushed the renovate/terraform-monorepo branch from ee8494b to 55d26ed Compare April 11, 2025 04:07

renovate bot changed the title ~~Update dependency hashicorp/terraform to v1.11.3~~ Update dependency hashicorp/terraform to v1.11.4 Apr 11, 2025

hmcts-jenkins-a-to-c bot added aat/destroy and removed aat/no-changes labels Apr 11, 2025

hmcts-jenkins-a-to-c bot requested a deployment to preview April 11, 2025 04:14 Abandoned

TomForniCGI closed this Apr 11, 2025

renovate bot deleted the renovate/terraform-monorepo branch April 11, 2025 15:03

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update dependency hashicorp/terraform to v1.11.4 #659

Update dependency hashicorp/terraform to v1.11.4 #659

Uh oh!

renovate bot commented Nov 21, 2024 •

edited

Loading

Uh oh!

hmcts-jenkins-a-to-c bot commented Nov 21, 2024 •

edited

Loading

Uh oh!

hmcts-jenkins-a-to-c bot commented Nov 21, 2024 •

edited

Loading

Uh oh!

renovate bot commented Apr 11, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Update dependency hashicorp/terraform to v1.11.4 #659

Update dependency hashicorp/terraform to v1.11.4 #659

Uh oh!

Conversation

renovate bot commented Nov 21, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

1.11.4 (April 9, 2025)

1.11.3 (March 26, 2025)

1.11.2 (March 12, 2025)

1.11.1 (March 5, 2025)

1.11.0 (February 27, 2025)

Previous Releases

1.10.5 (January 22, 2025)

1.10.4 (January 8, 2025)

1.10.3 (December 18, 2024)

1.10.2 (December 11, 2024)

1.10.1 (December 4, 2024)

1.10.0 (November 27, 2024)

Previous Releases

1.9.8 (October 16, 2024)

1.9.7 (October 2, 2024)

1.9.6 (September 18, 2024)

1.9.5 (August 20, 2024)

1.9.4 (August 7, 2024)

1.9.3 (July 24, 2024)

1.9.2 (July 10, 2024)

1.9.1 (July 3, 2024)

1.9.0 (June 26, 2024)

Previous Releases

1.8.5 (June 5, 2024)

1.8.4 (May 22, 2024)

1.8.3 (May 8, 2024)

1.8.2 (April 24, 2024)

1.8.1 (April 17, 2024)

1.8.0 (April 10, 2024)

Previous Releases

1.7.5 (March 13, 2024)

1.7.4 (February 21, 2024)

1.7.3 (February 7, 2024)

1.7.2 (January 31, 2024)

1.7.1 (January 24, 2024)

1.7.0 (January 17, 2024)

Previous Releases

1.6.6 (December 13, 2023)

1.6.5 (November 29, 2023)

1.6.4 (November 15, 2023)

1.6.3 (November 1, 2023)

Configuration

Uh oh!

hmcts-jenkins-a-to-c bot commented Nov 21, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Plan Result (aat)

⚠️ Resource Deletion will happen

Uh oh!

hmcts-jenkins-a-to-c bot commented Nov 21, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Plan Result (prod)

Uh oh!

renovate bot commented Apr 11, 2025

Renovate Ignore Notification

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Nov 21, 2024 •

edited

Loading

hmcts-jenkins-a-to-c bot commented Nov 21, 2024 •

edited

Loading

hmcts-jenkins-a-to-c bot commented Nov 21, 2024 •

edited

Loading