chore(deps): update dependency terraform to v1.10.0 #100

renovate · 2024-09-08T22:35:50Z

This PR contains the following updates:

Package	Update	Change
terraform	minor	`1.3.8` -> `1.10.0`

Release Notes

hashicorp/terraform (terraform)

`v1.10.0`

Compare Source

`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 (Unreleased)

UPGRADE NOTES:

Library used by Terraform (hashicorp/go-getter) for installing/updating modules was upgraded from v1.7.5 to v1.7.6. 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

`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" APIs. (#34127)

`v1.6.2`

Compare Source

1.6.2 (October 18, 2023)

BUG FIXES

terraform test: Fix performance issues when using provisioners within configs being tested. (#34026)
terraform test: Only process and parse relevant variables for each run block. (#34072)
Fix occasional crash when destroying configurations with variables containing validations. (#34101)
Fix interoperability issues between v1.6 series and earlier series by removing variable validations from the state file (#34058).
cloud: Fixes panic when saving state in Terraform Cloud when certain types of API errors are returned (#34074).
config: Fix crash in conditional statements with certain combinations of unknown values. Improve handling of refined values into the conditional expression results (#34096)
config: Update HCL to fix bug when decoding objects with optional attributes (#34108)
backend/s3: Some configurations would require -reconfigure during each init when config was not decoded correctly (#34108)

`v1.6.1`

Compare Source

1.6.1 (October 10, 2023)

ENHANCEMENTS:

backend/s3: The skip_requesting_account_id argument supports AWS API implementations that do not have the IAM, STS, or metadata API. (#34002)

BUG FIXES:

config: Using sensitive values as one or both of the results of a conditional expression will no longer crash. [GH-33996]
config: Conditional expression returning refined-non-null result will no longer crash. [GH-33996]
cli: Reverted back to previous behavior of ignoring signing key expiration for provider installation, since it's the provider registry's responsibility to verify key validity at publication time. [GH-34004]
cli: GIT_SSH_COMMAND is now preserved again when fetching modules from git source addresses. [GH-34045]
cloud: The TF_WORKSPACE environment variable works with the cloud block again; it can specify a workspace when none is configured, or select an active workspace when the config specifies tags. [GH-34012]
backend/s3: S3, DynamoDB, IAM, and STS endpoint parameters will no longer fail validation if the parsed scheme or hostname is empty. (#34017)
backend/s3: Providing a key alias to the kms_key_id argument will no longer fail validation. (#33993)

`v1.6.0`

Compare Source

1.6.0 (October 4, 2023)

UPGRADE NOTES:

On macOS, Terraform now requires macOS 10.15 Catalina or later; support for previous versions has been discontinued.
On Windows, Terraform now requires at least Windows 10 or Windows Server 2016; support for previous versions has been discontinued.
The S3 backend has a number of significant changes to its configuration format in this release, intended to match with recent changes in the hashicorp/aws provider:
- Configuration settings related to assuming IAM roles now belong to a nested block assume_role. The top-level arguments role_arn, session_name, external_id, assume_role_duration_seconds, assume_role_policy_arns, assume_role_tags, and assume_role_transitive_tag_keys are all now deprecated in favor of the nested equivalents. (#30495)
- Configuration settings related to overriding the locations of AWS service endpoints used by the provider now belong to a nested block endpoints. The top-level arguments dynamodb_endpoint, iam_endpoint, endpoint (fir S3), and sts_endpoint are now deprecated in favor of the nested equivalents. (#30492)
- The backend now uses the following environment variables for overriding the default locations of AWS service endpoints used by the provider: AWS_ENDPOINT_URL_DYNAMODB, AWS_ENDPOINT_URL_IAM, AWS_ENDPOINT_URL_S3, and AWS_ENDPOINT_URL_STS. The old non-standard names for these environment variables are now deprecated: AWS_DYNAMODB_ENDPOINT, AWS_IAM_ENDPOINT, AWS_S3_ENDPOINT, and AWS_STS_ENDPOINT. (#30479)
- The singular shared_credentials_file argument is deprecated in favor of the plural shared_credentials_files.
- The force_path_style argument is deprecated in favor of use_path_style for consistency with the AWS SDK. (#30491)

NEW FEATURES:

terraform test: The terraform test command is now generally available. This comes with a significant change to how tests are written and executed, based on feedback from the experimental phase.

Terraform tests are written in .tftest.hcl files, containing a series of run blocks. Each run block executes a Terraform plan and optional apply against the Terraform configuration under test and can check conditions against the resulting plan and state.

ENHANCEMENTS:

config: The import block id field now accepts expressions referring to other values such as resource attributes, as long as the value is a string known at plan time. (#33618)
Terraform Cloud integration: Remote plans on Terraform Cloud/Enterprise can now be saved using the -out option, viewed using terraform show, and applied using terraform apply with the saved plan filename. (#33492)
config: Terraform can now track some additional detail about values that won't be known until the apply step, such as the range of possible lengths for a collection or whether an unknown value can possibly be null.
core: Provider schemas can now be cached globally for compatible providers, allowing them to be reused throughout core without requesting them for each new provider instance. This can significantly reduce memory usage when there are many instances of the same provider in a single configuration (#33482)

When this information is available, Terraform can potentially generate known results for some operations on unknown values. This doesn't mean that Terraform can immediately track that detail in all cases, but the type system now supports that and so over time we can improve the level of detail generated by built-in functions, language operators, Terraform providers, etc. (#33234)
config: The try and can functions can now return more precise and consistent results when faced with unknown arguments (#33758)
terraform show -json: Now includes errored property, indicating whether the planning process halted with an error. An errored plan is not applyable. (#33372)
core: Terraform will now skip requesting the (possibly very large) provider schema from providers which indicate during handshake that they don't require that for correct behavior, in situations where Terraform Core itself does not need the schema. (#33486)
backend/kubernetes: The Kubernetes backend is no longer limited to storing states below 1MiB in size, and can now scale by splitting state across multiple secrets. (#29678)
backend/s3: Various improvements for consistency with hashicorp/aws provider capabilities:
- assume_role_with_web_identity nested block for assuming a role with dynamic credentials such as a JSON Web Token. (#31244)
- Now honors the standard AWS environment variables for credential and configuration files: AWS_CONFIG_FILE and AWS_SHARED_CREDENTIALS_FILE. (#30493)
- shared_config_files and shared_credentials_files arguments for specifying credential and configuration files as part of the backend configuration. (#30493)
- Internally the backend now uses AWS SDK for Go v2, which should address various other missing behaviors that are handled by the SDK rather than by Terraform itself. (#30443)
- custom_ca_bundle argument and support for the corresponding AWS environment variable, AWS_CA_BUNDLE, for providing custom root and intermediate certificates. (#33689)
- ec2_metadata_service_endpoint and ec2_metadata_service_endpoint_mode arguments and support for the corresponding AWS environment variables, AWS_EC2_METADATA_SERVICE_ENDPOINT and AWS_EC2_METADATA_SERVICE_ENDPOINT_MODE for setting the EC2 metadata service (IMDS) endpoint. The environment variable AWS_METADATA_URL is also supported for compatibility with the AWS provider, but is deprecated. (#30444)
- http_proxy, insecure, use_fips_endpoint, and use_dualstack_endpoint arguments and support for the corresponding environment variables, HTTP_PROXY and HTTPS_PROXY, which enable custom HTTP proxy configurations and the resolution of AWS endpoints with extended capabilities. (#30496)
- sts_region argument to use an alternative region for STS operations. (#33693)
- retry_mode argument and support for the corresponding AWS_RETRY_MODE environment variable to configure how retries are attempted. (#33692)
- allowed_account_ids and forbidden_account_ids arguments to prevent unintended modifications to specified environments. (#33688)
backend/cos: Support custom HTTP(S) endpoint and root domain for the API client. (#33656)

BUG FIXES:

core: Transitive dependencies were lost during apply when the referenced resource expanded into zero instances. (#33403)
cli: Terraform will no longer override SSH settings in local git configuration when installing modules. (#33592)
terraform built-in provider: The upstream dependency that Terraform uses for service discovery of Terraform-native services such as Terraform Cloud/Enterprise state storage was previously not concurrency-safe, but Terraform was treating it as if it was in situations like when a configuration has multiple terraform_remote_state blocks all using the "remote" backend. Terraform is now using a newer version of that library which updates its internal caches in a concurrency-safe way. (#33364)
terraform init: Terraform will no longer allow downloading remote modules to invalid paths. (#33745)
Ignore potential remote terraform version mismatch when running force-unlock (#28853)
cloud: Fixed a bug that would prevent nested symlinks from being dereferenced into the config sent to Terraform Cloud (#31895)
cloud: state snapshots could not be disabled when header x-terraform-snapshot-interval is absent (#33820)

Previous Releases

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

`v1.5.7`

Compare Source

1.5.7 (September 7, 2023)

BUG FIXES:

terraform init: Terraform will no longer allow downloading remote modules to invalid paths. (#33745)
terraform_remote_state: prevent future possible incompatibility with states which include unknown check block result kinds. (#33818)

`v1.5.6`

Compare Source

1.5.6 (August 23, 2023)

BUG FIXES:

terraform_remote_state: Fixed a potential unsafe read panic when reading from multiple terraform_remote_state data sources (#33333)

`v1.5.5`

Compare Source

1.5.5 (August 9, 2023)

terraform init: Fix crash when using invalid configuration in backend blocks. (#33628)

`v1.5.4`

Compare Source

1.5.4 (July 26, 2023)

BUG FIXES:

check blocks: Fixes crash when nested data sources are within configuration targeted by the terraform import command. (#33578)
check blocks: Check blocks now operate in line with other checkable objects by also executing during import operations. (#33578)

`v1.5.3`

Compare Source

1.5.3 (July 12, 2023)

BUG FIXES:

core: Terraform could fail to evaluate module outputs when they are used in a provider configuration during a destroy operation (#33462)
backend/consul: When failing to save state, consul CAS failed with transaction errors no longer shows an error instance memory address, but an actual error message. (#33108)
plan renderer: Fixes crash when rendering the plan if a relevant attribute contains an integer index specified as a string. (#33475)

`v1.5.2`

Compare Source

1.5.2 (June 28, 2023)

BUG FIXES:

configs: Multiple import blocks with the same id string no longer result in a validation error (#33434)

`v1.5.1`

Compare Source

1.5.1 (June 21, 2023)

BUG FIXES:

core: plan validation would fail for providers using nested set attributes with computed object attribute (#33377)

`v1.5.0`

Compare Source

1.5.0 (June 12, 2023)

NEW FEATURES:

check blocks for validating infrastructure: Module and configuration authors can now write independent check blocks within their configuration to validate assertions about their infrastructure.

The new independent check blocks must specify at least one assert block, but possibly many, each one with a condition expression and an error_message expression matching the existing Custom Condition Checks.
Additionally, check blocks can optionally load a scoped data source. Scoped data sources match the existing data sources with the exception that they can only be referenced from within their check block.

Unlike the existing precondition and postcondition blocks, Terraform will not halt execution should the scoped data block fail or error or if any of the assertions fail.
This allows practitioners to continually validate the state of their infrastructure outside the usual lifecycle management cycle.
import blocks for importing infrastructure: Root module authors can now use the import block to declare their intent that Terraform adopt an existing resource.

Import is now a configuration-driven, plannable action, and is processed as part of a normal plan. Running terraform plan will show a summary of the resources that Terraform has planned to import, along with any other plan changes.

The existing terraform import CLI command has not been modified.

This is an early version of the import block feature, for which we are actively seeking user feedback to shape future development. The import block currently does not support interpolation in the id field, which must be a string.
Generating configuration for imported resources: in conjunction with the import block, this feature enables easy templating of configuration when importing existing resources into Terraform. A new flag -generate-config-out=PATH is added to terraform plan. When this flag is set, Terraform will generate HCL configuration for any resource included in an import block that does not already have associated configuration, and write it to a new file at PATH. Before applying, review the generated configuration and edit it as necessary.
Adds a new plantimestamp function that returns the timestamp at plan time. This is similar to the timestamp function which returns the timestamp at apply time (#32980).
Adds a new strcontains function that checks whether a given string contains a given substring. (#33069)

UPGRADE NOTES:

This is the last version of Terraform for which macOS 10.13 High Sierra or 10.14 Mojave are officially supported. Future Terraform versions may not function correctly on these older versions of macOS.
This is the last version of Terraform for which Windows 7, 8, Server 2008, and Server 2012 are supported by Terraform's main implementation language, Go. We already ended explicit support for versions earlier than Windows 10 in Terraform v0.15.0, but future Terraform versions may malfunction in more significant ways on these older Windows versions.
On Linux (and some other non-macOS Unix platforms we don't officially support), Terraform will now notice the trust-ad option in /etc/resolv.conf and, if set, will set the "authentic data" option in outgoing DNS requests in order to better match the behavior of the GNU libc resolver.

Terraform does not pay any attention to the corresponding option in responses, but some DNSSEC-aware recursive resolvers return different responses when the request option isn't set. This should therefore avoid some potential situations where a DNS request from Terraform might get a different response than a similar request from other software on your system.

ENHANCEMENTS:

Terraform CLI's local operations mode will now attempt to persist state snapshots to the state storage backend periodically during the apply step, thereby reducing the window for lost data if the Terraform process is aborted unexpectedly. (#32680)
If Terraform CLI receives SIGINT (or its equivalent on non-Unix platforms) during the apply step then it will immediately try to persist the latest state snapshot to the state storage backend, with the assumption that a graceful shutdown request often typically followed by a hard abort some time later if the graceful shutdown doesn't complete fast enough. (#32680)
pg backend: Now supports the PG_CONN_STR, PG_SCHEMA_NAME, PG_SKIP_SCHEMA_CREATION, PG_SKIP_TABLE_CREATION and PG_SKIP_INDEX_CREATION environment variables. (#33045)

BUG FIXES:

terraform init: Fixed crash with invalid blank module name. (#32781)
moved blocks: Fixed a typo in the error message that Terraform raises when you use -target to exclude an object that has been moved. (#33149)

Previous Releases

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

`v1.4.7`

Compare Source

1.4.7 (September 13, 2023)

BUG FIXES:

terraform_remote_state: fix incompatibility with states produced by Terraform 1.5 or later which include check block results. (#33814)

`v1.4.6`

Compare Source

1.4.6 (April 26, 2023)

BUG FIXES

Fix bug when rendering plans that include null strings. (#33029)
Fix bug when rendering plans that include unknown values in maps. (#33029)
Fix bug where the plan would render twice when using older versions of TFE as a backend. (#33018)
Fix bug where sensitive and unknown metadata was not being propagated to dynamic types while rendering plans. (#33057)
Fix bug where sensitive metadata from the schema was not being included in the terraform show -json output. (#33059)
Fix bug where computed attributes were not being rendered with the # forces replacement suffix. ([#33065](https://redirect.github.com/hashi

Configuration

📅 Schedule: Branch creation - "every 2 weeks on Monday before 7am" in timezone Europe/Berlin, 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 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.

renovate bot requested a review from ff6347 as a code owner September 8, 2024 22:35

renovate bot force-pushed the renovate/terraform-monorepo branch from 19a4584 to 25d6b2f Compare September 18, 2024 10:44

renovate bot changed the title ~~chore(deps): update dependency terraform to v1.9.5~~ chore(deps): update dependency terraform to v1.9.6 Sep 18, 2024

renovate bot force-pushed the renovate/terraform-monorepo branch from 25d6b2f to 3b09b2e Compare September 24, 2024 05:01

renovate bot changed the title ~~chore(deps): update dependency terraform to v1.9.6~~ chore(deps): update dependency terraform to v1.9.7 Oct 2, 2024

renovate bot force-pushed the renovate/terraform-monorepo branch from 3b09b2e to 46c2f23 Compare October 2, 2024 19:40

renovate bot force-pushed the renovate/terraform-monorepo branch from 46c2f23 to 60c02ee Compare October 16, 2024 17:00

renovate bot changed the title ~~chore(deps): update dependency terraform to v1.9.7~~ chore(deps): update dependency terraform to v1.9.8 Oct 16, 2024

chore(deps): update dependency terraform to v1.10.0

674e14d

renovate bot force-pushed the renovate/terraform-monorepo branch from 60c02ee to 674e14d Compare November 27, 2024 13:48

renovate bot changed the title ~~chore(deps): update dependency terraform to v1.9.8~~ chore(deps): update dependency terraform to v1.10.0 Nov 27, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency terraform to v1.10.0 #100

chore(deps): update dependency terraform to v1.10.0 #100

renovate bot commented Sep 8, 2024 •

edited

Loading

chore(deps): update dependency terraform to v1.10.0 #100

Are you sure you want to change the base?

chore(deps): update dependency terraform to v1.10.0 #100

Conversation

renovate bot commented Sep 8, 2024 • edited Loading

Release Notes

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 (Unreleased)

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)

1.6.2 (October 18, 2023)

1.6.1 (October 10, 2023)

1.6.0 (October 4, 2023)

Previous Releases

1.5.7 (September 7, 2023)

1.5.6 (August 23, 2023)

1.5.5 (August 9, 2023)

1.5.4 (July 26, 2023)

1.5.3 (July 12, 2023)

1.5.2 (June 28, 2023)

1.5.1 (June 21, 2023)

1.5.0 (June 12, 2023)

Previous Releases

1.4.7 (September 13, 2023)

1.4.6 (April 26, 2023)

Configuration

renovate bot commented Sep 8, 2024 •

edited

Loading