renovate[bot]
commented
2 months ago Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (1.7.5). 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.
This PR contains the following updates:
1.3.7->1.7.5Release Notes
hashicorp/terraform (hashicorp/terraform)
### [`v1.7.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.7.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.7.4...v1.7.5) ##### 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](https://togithub.com/hashicorp/terraform/pull/34796)) ### [`v1.7.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.7.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.7.3...v1.7.4) #### 1.7.4 (February 21, 2024) BUG FIXES: - `terraform test`: Fix automatic loading of variable files within the test directory on `windows` platforms. ([#34666](https://togithub.com/hashicorp/terraform/pull/34666)) - plan renderer: Very large numbers (> 2^63) will no longer be truncated in the human-readable plan. ([#34702](https://togithub.com/hashicorp/terraform/pull/34702)) ### [`v1.7.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.7.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.7.2...v1.7.3) ##### 1.7.3 (February 7, 2024) BUG FIXES: - `terraform test`: Fix crash when dynamic-typed attributes are not assigned values in mocks. ([#34610](https://togithub.com/hashicorp/terraform/pull/34511)) - provisioners/file: Fix panic when source is null. ([#34621](https://togithub.com/hashicorp/terraform/pull/34621)) - `import`: Throw helpful error message if an import block is configured with an empty ID ([34625](https://togithub.com/hashicorp/terraform/pull/34625)) ### [`v1.7.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.7.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.7.1...v1.7.2) ##### 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](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/issues/34543)) ENHANCEMENTS: - `terraform fmt`: Terraform mock data files (`.tfmock.hcl`) will now be included when executing the format command. ([#34580](https://togithub.com/hashicorp/terraform/issues/34580)) - Add additional diagnostics when a generated provider block that fails schema validation requires explicit configuration. ([#34595](https://togithub.com/hashicorp/terraform/issues/34595)) ### [`v1.7.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.7.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.7.0...v1.7.1) ##### 1.7.1 (January 24, 2024) BUG FIXES: - `terraform test`: Fix crash when referencing variables or functions within the file level `variables` block. ([#34531](https://togithub.com/hashicorp/terraform/issues/34531)) - `terraform test`: Fix crash when `override_module` block was missing the `outputs` attribute. ([#34563](https://togithub.com/hashicorp/terraform/issues/34563)) ### [`v1.7.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.7.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.6.6...v1.7.0) ##### 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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/28853)) - Exit Dockerfile build script early on `cd` failure. ([#34128](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/pull/34331)) - `terraform test`: Improve error message for invalid run block names. ([#34469](https://togithub.com/hashicorp/terraform/pull/34469)) - `terraform test`: Fix bug where outputs in "empty" modules were not available to the assertions from Terraform test files. ([#34482](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/issues/34426)) ENHANCEMENTS: - `terraform test`: Providers defined within test files can now reference variables from their configuration that are defined within the test file. ([#34069](https://togithub.com/hashicorp/terraform/issues/34069)) - `terraform test`: Providers defined within test files can now reference outputs from run blocks. ([#34118](https://togithub.com/hashicorp/terraform/issues/34118)) - `terraform test`: Terraform functions are now available within variables and provider blocks within test files. ([#34204](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/pull/34341)) - `terraform graph`: Now produces a simplified resources-only graph by default. ([#34288](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/issues/34342)) - `import`: `for_each` can now be used to expand the `import` block to handle multiple resource instances ([#33932](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/34312)) - `.terraformignore`: improve performance when ignoring large directories ([#34400](https://togithub.com/hashicorp/terraform/pull/34400)) ##### Previous Releases For information on prior major and minor releases, see their changelogs: - [v1.6](https://togithub.com/hashicorp/terraform/blob/v1.6/CHANGELOG.md) - [v1.5](https://togithub.com/hashicorp/terraform/blob/v1.5/CHANGELOG.md) - [v1.4](https://togithub.com/hashicorp/terraform/blob/v1.4/CHANGELOG.md) - [v1.3](https://togithub.com/hashicorp/terraform/blob/v1.3/CHANGELOG.md) - [v1.2](https://togithub.com/hashicorp/terraform/blob/v1.2/CHANGELOG.md) - [v1.1](https://togithub.com/hashicorp/terraform/blob/v1.1/CHANGELOG.md) - [v1.0](https://togithub.com/hashicorp/terraform/blob/v1.0/CHANGELOG.md) - [v0.15](https://togithub.com/hashicorp/terraform/blob/v0.15/CHANGELOG.md) - [v0.14](https://togithub.com/hashicorp/terraform/blob/v0.14/CHANGELOG.md) - [v0.13](https://togithub.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md) - [v0.12](https://togithub.com/hashicorp/terraform/blob/v0.12/CHANGELOG.md) - [v0.11 and earlier](https://togithub.com/hashicorp/terraform/blob/v0.11/CHANGELOG.md) ### [`v1.6.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.6.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.6.5...v1.6.6) #### 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](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/issues/34380)) ### [`v1.6.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.6.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.6.4...v1.6.5) #### 1.6.5 (November 29, 2023) BUG FIXES: - backend/s3: Fixes parsing errors in shared config and credentials files. ([#34313](https://togithub.com/hashicorp/terraform/pull/34313)) - backend/s3: Fixes error with AWS SSO when using FIPS endpoints. ([#34313](https://togithub.com/hashicorp/terraform/pull/34313)) ### [`v1.6.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.6.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.6.3...v1.6.4) #### 1.6.4 (November 15, 2023) ENHANCEMENTS: - backend/s3: Add the parameter `endpoints.sso` to allow overriding the AWS SSO API endpoint. ([#34195](https://togithub.com/hashicorp/terraform/pull/34195)) BUG FIXES: - `terraform test`: Fix bug preventing passing sensitive output values from previous run blocks as inputs to future run blocks. ([#34190](https://togithub.com/hashicorp/terraform/pull/34190)) - backend/s3: Add `https_proxy` and `no_proxy` parameters to allow fully specifying proxy configuration ([#34243](https://togithub.com/hashicorp/terraform/pull/34243)) ### [`v1.6.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.6.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.6.2...v1.6.3) #### 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](https://togithub.com/hashicorp/terraform/pull/34127)) ### [`v1.6.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.6.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.6.1...v1.6.2) #### 1.6.2 (October 18, 2023) BUG FIXES - `terraform test`: Fix performance issues when using provisioners within configs being tested. ([#34026](https://togithub.com/hashicorp/terraform/pull/34026)) - `terraform test`: Only process and parse relevant variables for each run block. ([#34072](https://togithub.com/hashicorp/terraform/pull/34072)) - Fix occasional crash when destroying configurations with variables containing validations. ([#34101](https://togithub.com/hashicorp/terraform/pull/34101)) - Fix interoperability issues between v1.6 series and earlier series by removing variable validations from the state file ([#34058](https://togithub.com/hashicorp/terraform/pull/34058)). - cloud: Fixes panic when saving state in Terraform Cloud when certain types of API errors are returned ([#34074](https://togithub.com/hashicorp/terraform/pull/34074)). - config: Fix crash in conditional statements with certain combinations of unknown values. Improve handling of refined values into the conditional expression results ([#34096](https://togithub.com/hashicorp/terraform/issues/34096)) - config: Update HCL to fix bug when decoding objects with optional attributes ([#34108](https://togithub.com/hashicorp/terraform/issues/34108)) - backend/s3: Some configurations would require `-reconfigure` during each `init` when config was not decoded correctly ([#34108](https://togithub.com/hashicorp/terraform/issues/34108)) ### [`v1.6.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.6.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.6.0...v1.6.1) #### 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](https://togithub.com/hashicorp/terraform/pull/34002)) BUG FIXES: - config: Using sensitive values as one or both of the results of a conditional expression will no longer crash. \[[GH-33996](https://togithub.com/hashicorp/terraform/issues/33996)] - config: Conditional expression returning refined-non-null result will no longer crash. \[[GH-33996](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/34004)] - cli: `GIT_SSH_COMMAND` is now preserved again when fetching modules from git source addresses. \[[GH-34045](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/34012)] - backend/s3: S3, DynamoDB, IAM, and STS endpoint parameters will no longer fail validation if the parsed scheme or hostname is empty. ([#34017](https://togithub.com/hashicorp/terraform/pull/34017)) - backend/s3: Providing a key alias to the `kms_key_id` argument will no longer fail validation. ([#33993](https://togithub.com/hashicorp/terraform/pull/33993)) ### [`v1.6.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.6.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.5.7...v1.6.0) #### 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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/issues/33234)) - config: The `try` and `can` functions can now return more precise and consistent results when faced with unknown arguments ([#33758](https://togithub.com/hashicorp/terraform/pull/33758)) - `terraform show -json`: Now includes `errored` property, indicating whether the planning process halted with an error. An errored plan is not applyable. ([#33372](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/issues/31244)) - Now honors the standard AWS environment variables for credential and configuration files: `AWS_CONFIG_FILE` and `AWS_SHARED_CREDENTIALS_FILE`. ([#30493](https://togithub.com/hashicorp/terraform/issues/30493)) - `shared_config_files` and `shared_credentials_files` arguments for specifying credential and configuration files as part of the backend configuration. ([#30493](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/30443)) - `custom_ca_bundle` argument and support for the corresponding AWS environment variable, `AWS_CA_BUNDLE`, for providing custom root and intermediate certificates. ([#33689](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/30496)) - `sts_region` argument to use an alternative region for STS operations. ([#33693](https://togithub.com/hashicorp/terraform/issues/33693)) - `retry_mode` argument and support for the corresponding `AWS_RETRY_MODE` environment variable to configure how retries are attempted. ([#33692](https://togithub.com/hashicorp/terraform/issues/33692)) - `allowed_account_ids` and `forbidden_account_ids` arguments to prevent unintended modifications to specified environments. ([#33688](https://togithub.com/hashicorp/terraform/issues/33688)) - backend/cos: Support custom HTTP(S) endpoint and root domain for the API client. ([#33656](https://togithub.com/hashicorp/terraform/issues/33656)) BUG FIXES: - core: Transitive dependencies were lost during apply when the referenced resource expanded into zero instances. ([#33403](https://togithub.com/hashicorp/terraform/issues/33403)) - cli: Terraform will no longer override SSH settings in local git configuration when installing modules. ([#33592](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/33364)) - `terraform init`: Terraform will no longer allow downloading remote modules to invalid paths. ([#33745](https://togithub.com/hashicorp/terraform/issues/33745)) - Ignore potential remote terraform version mismatch when running force-unlock ([#28853](https://togithub.com/hashicorp/terraform/issues/28853)) - cloud: Fixed a bug that would prevent nested symlinks from being dereferenced into the config sent to Terraform Cloud ([#31895](https://togithub.com/hashicorp/terraform/issues/31895)) - cloud: state snapshots could not be disabled when header x-terraform-snapshot-interval is absent ([#33820](https://togithub.com/hashicorp/terraform/pull/33820)) #### Previous Releases For information on prior major and minor releases, see their changelogs: - [v1.5](https://togithub.com/hashicorp/terraform/blob/v1.5/CHANGELOG.md) - [v1.4](https://togithub.com/hashicorp/terraform/blob/v1.4/CHANGELOG.md) - [v1.3](https://togithub.com/hashicorp/terraform/blob/v1.3/CHANGELOG.md) - [v1.2](https://togithub.com/hashicorp/terraform/blob/v1.2/CHANGELOG.md) - [v1.1](https://togithub.com/hashicorp/terraform/blob/v1.1/CHANGELOG.md) - [v1.0](https://togithub.com/hashicorp/terraform/blob/v1.0/CHANGELOG.md) - [v0.15](https://togithub.com/hashicorp/terraform/blob/v0.15/CHANGELOG.md) - [v0.14](https://togithub.com/hashicorp/terraform/blob/v0.14/CHANGELOG.md) - [v0.13](https://togithub.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md) - [v0.12](https://togithub.com/hashicorp/terraform/blob/v0.12/CHANGELOG.md) - [v0.11 and earlier](https://togithub.com/hashicorp/terraform/blob/v0.11/CHANGELOG.md) ### [`v1.5.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.5.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.5.6...v1.5.7) #### 1.5.7 (September 7, 2023) BUG FIXES: - `terraform init`: Terraform will no longer allow downloading remote modules to invalid paths. ([#33745](https://togithub.com/hashicorp/terraform/issues/33745)) - `terraform_remote_state`: prevent future possible incompatibility with states which include unknown `check` block result kinds. ([#33818](https://togithub.com/hashicorp/terraform/issues/33818)) ### [`v1.5.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.5.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.5.5...v1.5.6) #### 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](https://togithub.com/hashicorp/terraform/issues/33333)) ### [`v1.5.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.5.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.5.4...v1.5.5) ##### 1.5.5 (August 9, 2023) - `terraform init`: Fix crash when using invalid configuration in backend blocks. ([#33628](https://togithub.com/hashicorp/terraform/issues/33628)) ### [`v1.5.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.5.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.5.3...v1.5.4) #### 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](https://togithub.com/hashicorp/terraform/issues/33578)) - `check` blocks: Check blocks now operate in line with other checkable objects by also executing during import operations. ([#33578](https://togithub.com/hashicorp/terraform/issues/33578)) ### [`v1.5.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.5.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.5.2...v1.5.3) #### 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](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/pull/33108)) - plan renderer: Fixes crash when rendering the plan if a relevant attribute contains an integer index specified as a string. ([#33475](https://togithub.com/hashicorp/terraform/issues/33475)) ### [`v1.5.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.5.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.5.1...v1.5.2) #### 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](https://togithub.com/hashicorp/terraform/issues/33434)) ### [`v1.5.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.5.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.5.0...v1.5.1) ##### 1.5.1 (June 21, 2023) BUG FIXES: - core: plan validation would fail for providers using nested set attributes with computed object attribute ([#33377](https://togithub.com/hashicorp/terraform/issues/33377)) ### [`v1.5.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.5.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.4.7...v1.5.0) #### 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](https://developer.hashicorp.com/terraform/language/v1.4.x/expressions/custom-conditions). Additionally, check blocks can optionally load a scoped [data source](https://developer.hashicorp.com/terraform/language/v1.4.x/data-sources). 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](https://togithub.com/hashicorp/terraform/pull/32980)). - Adds a new `strcontains` function that checks whether a given string contains a given substring. ([#33069](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/33045)) BUG FIXES: - `terraform init`: Fixed crash with invalid blank module name. ([#32781](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/33149)) #### Previous Releases For information on prior major and minor releases, see their changelogs: - [v1.4](https://togithub.com/hashicorp/terraform/blob/v1.4/CHANGELOG.md) - [v1.3](https://togithub.com/hashicorp/terraform/blob/v1.3/CHANGELOG.md) - [v1.2](https://togithub.com/hashicorp/terraform/blob/v1.2/CHANGELOG.md) - [v1.1](https://togithub.com/hashicorp/terraform/blob/v1.1/CHANGELOG.md) - [v1.0](https://togithub.com/hashicorp/terraform/blob/v1.0/CHANGELOG.md) - [v0.15](https://togithub.com/hashicorp/terraform/blob/v0.15/CHANGELOG.md) - [v0.14](https://togithub.com/hashicorp/terraform/blob/v0.14/CHANGELOG.md) - [v0.13](https://togithub.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md) - [v0.12](https://togithub.com/hashicorp/terraform/blob/v0.12/CHANGELOG.md) - [v0.11 and earlier](https://togithub.com/hashicorp/terraform/blob/v0.11/CHANGELOG.md) ### [`v1.4.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.4.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.4.6...v1.4.7) #### 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](https://togithub.com/hashicorp/terraform/pull/33814)) ### [`v1.4.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.4.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.4.5...v1.4.6) #### 1.4.6 (April 26, 2023) BUG FIXES - Fix bug when rendering plans that include null strings. ([#33029](https://togithub.com/hashicorp/terraform/issues/33029)) - Fix bug when rendering plans that include unknown values in maps. ([#33029](https://togithub.com/hashicorp/terraform/issues/33029)) - Fix bug where the plan would render twice when using older versions of TFE as a backend. ([#33018](https://togithub.com/hashicorp/terraform/issues/33018)) - Fix bug where sensitive and unknown metadata was not being propagated to dynamic types while rendering plans. ([#33057](https://togithub.com/hashicorp/terraform/issues/33057)) - Fix bug where sensitive metadata from the schema was not being included in the `terraform show -json` output. ([#33059](https://togithub.com/hashicorp/terraform/issues/33059)) - Fix bug where computed attributes were not being rendered with the `# forces replacement` suffix. ([#33065](https://togithub.com/hashicorp/terraform/issues/33065)) ### [`v1.4.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.4.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.4.4...v1.4.5) #### 1.4.5 (April 12, 2023) - Revert change from \[[#32892](https://togithub.com/hashicorp/terraform/issues/32892)] due to an upstream crash. - Fix planned destroy value which would cause `terraform_data` to fail when being replaced with `create_before_destroy` ([#32988](https://togithub.com/hashicorp/terraform/issues/32988)) ### [`v1.4.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.4.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.4.3...v1.4.4) #### 1.4.4 (March 30, 2023) Due to an incident while migrating build systems for the 1.4.3 release where `CGO_ENABLED=0` was not set, we are rebuilding that version as 1.4.4 with the flag set. No other changes have been made between 1.4.3 and 1.4.4. ### [`v1.4.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.4.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.4.2...v1.4.3) #### 1.4.3 (March 30, 2023) BUG FIXES: - Prevent sensitive values in non-root module outputs from marking the entire output as sensitive \[[GH-32891](https://togithub.com/hashicorp/terraform/issues/32891)] - Fix the handling of planned data source objects when storing a failed plan \[[GH-32876](https://togithub.com/hashicorp/terraform/issues/32876)] - Don't fail during plan generation when targeting prevents resources with schema changes from performing a state upgrade \[[GH-32900](https://togithub.com/hashicorp/terraform/issues/32900)] - Skip planned changes in sensitive marks when the changed attribute is discarded by the provider \[[GH-32892](https://togithub.com/hashicorp/terraform/issues/32892)] ### [`v1.4.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.4.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.4.1...v1.4.2) #### 1.4.2 (March 16, 2023) BUG FIXES: - Fix bug in which certain uses of `setproduct` caused Terraform to crash ([#32860](https://togithub.com/hashicorp/terraform/issues/32860)) - Fix bug in which some provider plans were not being calculated correctly, leading to an "invalid plan" error ([#32860](https://togithub.com/hashicorp/terraform/issues/32860)) ### [`v1.4.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.4.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.4.0...v1.4.1) #### 1.4.1 (March 15, 2023) BUG FIXES: - Enables overriding modules that have the `depends_on` attribute set, while still preventing the `depends_on` attribute itself from being overridden. ([#32796](https://togithub.com/hashicorp/terraform/issues/32796)) - `terraform providers mirror`: when a dependency lock file is present, mirror the resolved providers versions, not the latest available based on configuration. ([#32749](https://togithub.com/hashicorp/terraform/issues/32749)) - Fixed module downloads from S3 URLs when using AWS IAM roles for service accounts (IRSA). ([#32700](https://togithub.com/hashicorp/terraform/issues/32700)) - hcl: Fix a crash in Terraform when attempting to apply defaults into an incompatible type. ([#32775](https://togithub.com/hashicorp/terraform/issues/32775)) - Prevent panic when creating a plan which errors before the planning process has begun. ([#32818](https://togithub.com/hashicorp/terraform/issues/32818)) - Fix the plan renderer skipping the "no changes" messages when there are no-op outputs within the plan. ([#32820](https://togithub.com/hashicorp/terraform/issues/32820)) - Prevent panic when rendering null nested primitive values in a state output. ([#32840](https://togithub.com/hashicorp/terraform/issues/32840)) - Warn when an invalid path is specified in `TF_CLI_CONFIG_FILE` ([#32846](https://togithub.com/hashicorp/terraform/issues/32846)) ### [`v1.4.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.4.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.10...v1.4.0) #### 1.4.0 (March 08, 2023) UPGRADE NOTES: - config: The `textencodebase64` function when called with encoding "GB18030" will now encode the euro symbol € as the two-byte sequence `0xA2,0xE3`, as required by the GB18030 standard, before applying base64 encoding. - config: The `textencodebase64` function when called with encoding "GBK" or "CP936" will now encode the euro symbol € as the single byte `0x80` before applying base64 encoding. This matches the behavior of the Windows API when encoding to this Windows-specific character encoding. - `terraform init`: When interpreting the hostname portion of a provider source address or the address of a module in a module registry, Terraform will now use *non-transitional* IDNA2008 mapping rules instead of the transitional mapping rules previously used. This matches a change to [the WHATWG URL spec's rules for interpreting non-ASCII domain names](https://url.spec.whatwg.org/#concept-domain-to-ascii) which is being gradually adopted by web browsers. Terraform aims to follow the interpretation of hostnames used by web browsers for consistency. For some hostnames containing non-ASCII characters this may cause Terraform to now request a different "punycode" hostname when resolving. - `terraform init` will now ignore entries in the optional global provider cache directory unless they match a checksum already tracked in the current configuration's dependency lock file. This therefore avoids the long-standing problem that when installing a new provider for the first time from the cache we can't determine the full set of checksums to include in the lock file. Once the lock file has been updated to include a checksum covering the item in the global cache, Terraform will then use the cache entry for subsequent installation of the same provider package. There is an interim CLI configuration opt-out for those who rely on the previous incorrect behavior. ([#32129](https://togithub.com/hashicorp/terraform/issues/32129)) - The Terraform plan renderer has been completely rewritten to aid with future Terraform Cloud integration. Users should not see any material change in the plan output between 1.3 and 1.4. If you notice any significant differences, or if Terraform fails to plan successfully due to rendering problems, please open a bug report issue. BUG FIXES: - The module installer will now record in its manifest a correct module source URL after normalization when the URL given as input contains both a query string portion and a subdirectory portion. Terraform itself doesn't currently make use of this information and so this is just a cosmetic fix to make the recorded metadata more correct. ([#31636](https://togithub.com/hashicorp/terraform/issues/31636)) - config: The `yamldecode` function now correctly handles entirely-nil YAML documents. Previously it would incorrectly return an unknown value instead of a null value. It will now return a null value as documented. ([#32151](https://togithub.com/hashicorp/terraform/issues/32151)) - Ensure correct ordering between data sources and the deletion of managed resource dependencies. ([#32209](https://togithub.com/hashicorp/terraform/issues/32209)) - Fix Terraform creating objects that should not exist in variables that specify default attributes in optional objects. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Fix several Terraform crashes that are caused by HCL creating objects that should not exist in variables that specify default attributes in optional objects within collections. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Fix inconsistent behaviour in empty vs null collections. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - `terraform workspace` now returns a non-zero exit when given an invalid argument ([#31318](https://togithub.com/hashicorp/terraform/issues/31318)) - Terraform would always plan changes when using a nested set attribute ([#32536](https://togithub.com/hashicorp/terraform/issues/32536)) - Terraform can now better detect when complex optional+computed object attributes are removed from configuration ([#32551](https://togithub.com/hashicorp/terraform/issues/32551)) - A new methodology for planning set elements can now better detect optional+computed changes within sets ([#32563](https://togithub.com/hashicorp/terraform/issues/32563)) - Fix state locking and releasing messages when in `-json` mode, messages will now be written in JSON format ([#32451](https://togithub.com/hashicorp/terraform/issues/32451)) ENHANCEMENTS: - `terraform plan` can now store a plan file even when encountering errors, which can later be inspected to help identify the source of the failures ([#32395](https://togithub.com/hashicorp/terraform/issues/32395)) - `terraform_data` is a new builtin managed resource type, which can replace the use of `null_resource`, and can store data of any type ([#31757](https://togithub.com/hashicorp/terraform/issues/31757)) - `terraform init` will now ignore entries in the optional global provider cache directory unless they match a checksum already tracked in the current configuration's dependency lock file. This therefore avoids the long-standing problem that when installing a new provider for the first time from the cache we can't determine the full set of checksums to include in the lock file. Once the lock file has been updated to include a checksum covering the item in the global cache, Terraform will then use the cache entry for subsequent installation of the same provider package. There is an interim CLI configuration opt-out for those who rely on the previous incorrect behavior. ([#32129](https://togithub.com/hashicorp/terraform/issues/32129)) - Interactive input for sensitive variables is now masked in the UI ([#29520](https://togithub.com/hashicorp/terraform/issues/29520)) - A new `-or-create` flag was added to `terraform workspace select`, to aid in creating workspaces in automated situations ([#31633](https://togithub.com/hashicorp/terraform/issues/31633)) - A new command was added for exporting Terraform function signatures in machine-readable format: `terraform metadata functions -json` ([#32487](https://togithub.com/hashicorp/terraform/issues/32487)) - The "Failed to install provider" error message now includes the reason a provider could not be installed. ([#31898](https://togithub.com/hashicorp/terraform/issues/31898)) - backend/gcs: Add `kms_encryption_key` argument, to allow encryption of state files using Cloud KMS keys. ([#24967](https://togithub.com/hashicorp/terraform/issues/24967)) - backend/gcs: Add `storage_custom_endpoint` argument, to allow communication with the backend via a Private Service Connect endpoint. ([#28856](https://togithub.com/hashicorp/terraform/issues/28856)) - backend/gcs: Update documentation for usage of `gcs` with `terraform_remote_state` ([#32065](https://togithub.com/hashicorp/terraform/issues/32065)) - backend/gcs: Update storage package to v1.28.0 ([#29656](https://togithub.com/hashicorp/terraform/issues/29656)) - When removing a workspace from the `cloud` backend `terraform workspace delete` will use Terraform Cloud's [Safe Delete](https://developer.hashicorp.com/terraform/cloud-docs/api-docs/workspaces#safe-delete-a-workspace) API if the `-force` flag is not provided. ([#31949](https://togithub.com/hashicorp/terraform/pull/31949)) - backend/oss: More robustly handle endpoint retrieval error ([#32295](https://togithub.com/hashicorp/terraform/issues/32295)) - local-exec provisioner: Added `quiet` argument. If `quiet` is set to `true`, Terraform will not print the entire command to stdout during plan. ([#32116](https://togithub.com/hashicorp/terraform/issues/32116)) - backend/http: Add support for mTLS authentication. ([#31699](https://togithub.com/hashicorp/terraform/issues/31699)) - cloud: Add support for using the [generic hostname](https://developer.hashicorp.com/terraform/cloud-docs/registry/using#generic-hostname-terraform-enterprise) localterraform.com in module and provider sources as a substitute for the currently configured cloud backend hostname. This enhancement was also applied to the remote backend. - `terraform show` will now print an explanation when called on a Terraform workspace with empty state detailing why no resources are shown. ([#32629](https://togithub.com/hashicorp/terraform/issues/32629)) - backend/gcs: Added support for `GOOGLE_BACKEND_IMPERSONATE_SERVICE_ACCOUNT` env var to allow impersonating a different service account when `GOOGLE_IMPERSONATE_SERVICE_ACCOUNT` is configured for the GCP provider. ([#32557](https://togithub.com/hashicorp/terraform/issues/32557)) - backend/cos: Add support for the `assume_role` authentication method with the `tencentcloud` provider. This can be configured via the Terraform config or environment variables. - backend/cos: Add support for the `security_token` authentication method with the `tencentcloud` provider. This can be configured via the Terraform config or environment variables. EXPERIMENTS: - Since its introduction the `yamlencode` function's documentation carried a warning that it was experimental. This predated our more formalized idea of language experiments and so wasn't guarded by an explicit opt-in, but the intention was to allow for small adjustments to its behavior if we learned it was producing invalid YAML in some cases, due to the relative complexity of the YAML specification. From Terraform v1.4 onwards, `yamlencode` is no longer documented as experimental and is now subject to the Terraform v1.x Compatibility Promises. There are no changes to its previous behavior in v1.3 and so no special action is required when upgrading. ### [`v1.3.10`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.10) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.9...v1.3.10) ##### 1.3.10 (September 13, 2023) BUG FIXES: - `terraform_remote_state`: fix incompatibility with states produced by Terraform 1.5 or later which include `check` block results. ([#33813](https://togithub.com/hashicorp/terraform/pull/33813)) ### [`v1.3.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.8...v1.3.9) #### 1.3.9 (February 15, 2023) BUG FIXES: - Fix crash when planning to remove already-deposed resource instances. ([#32663](https://togithub.com/hashicorp/terraform/issues/32663)) ### [`v1.3.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.7...v1.3.8) #### 1.3.8 (February 09, 2023) BUG FIXES: - Fixed a rare bug causing inaccurate `before_sensitive` / `after_sensitive` annotations in JSON plan output for deeply nested structures. This was only observed in the wild on the rancher/rancher2 provider, and resulted in glitched display in Terraform Cloud's structured plan log view. ([#32543](https://togithub.com/hashicorp/terraform/issues/32543)) - A variable only referenced by an output precondition error_message may be missing during evaluation ([#32464](https://togithub.com/hashicorp/terraform/issues/32464)) - Removing a NestingSingle block from configuration results in an invalid plan ([#32463](https://togithub.com/hashicorp/terraform/issues/32463)) - Null module outputs could be dropped, causing evaluation errors when referring to those module attributes ([#32583](https://togithub.com/hashicorp/terraform/issues/32583)) - Fix terraform crash when applying defaults into a collection with dynamic type constraint. ([#32454](https://togithub.com/hashicorp/terraform/issues/32454)) - Updated to newer github.com/mitchellh/cli version, in turn bringing in updates for several indirect dependencies with known security issues. ([#32609](https://togithub.com/hashicorp/terraform/issues/32609)) - Fix case where the first plan to use a new remote state could be applied twice, corrupting the state ([#32614](https://togithub.com/hashicorp/terraform/issues/32614))Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.