chore(deps): update ⬆️ golang module github.com/hashicorp/terraform to v1

This PR contains the following updates:

Package	Type	Update	Change
github.com/hashicorp/terraform	require	major	`v0.12.17` -> `v1.2.9`

Release Notes

hashicorp/terraform

### [`v1.2.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.8...v1.2.9) #### 1.2.9 (September 07, 2022) ENHANCEMENTS: - terraform init: add link to documentation when a checksum is missing from the lock file. ([#31726](https://togithub.com/hashicorp/terraform/issues/31726)) ### [`v1.2.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.7...v1.2.8) #### 1.2.8 (August 24, 2022) BUG FIXES: - config: The `flatten` function will no longer panic if given a null value that has been explicitly converted to or implicitly inferred as having a list, set, or tuple type. Previously Terraform would panic in such a situation because it tried to "flatten" the contents of the null value into the result, which is impossible. ([#31675](https://togithub.com/hashicorp/terraform/issues/31675)) - config: The `tolist`, `toset`, and `tomap` functions, and various automatic conversions that include similar logic, will no longer panic when asked to infer an element type that is convertable from both a tuple type and a list type whose element type is not yet known. ([#31675](https://togithub.com/hashicorp/terraform/issues/31675)) ### [`v1.2.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.6...v1.2.7) #### 1.2.7 (August 10, 2022) ENHANCEMENTS: - config: Check for direct references to deprecated computed attributes. ([#31576](https://togithub.com/hashicorp/terraform/issues/31576)) BUG FIXES: - config: Fix an crash if a submodule contains a resource whose implied provider local name contains invalid characters, by adding additional validation rules to turn it into a real error. ([#31573](https://togithub.com/hashicorp/terraform/issues/31573)) - core: Fix some handling of provider schema attributes which use the newer "structural typing" mechanism introduced with protocol version 6, and therefore with the new Terraform Plugin Framework ([#31532](https://togithub.com/hashicorp/terraform/issues/31532)) - command: Add missing output text for applyable refresh plans. ([#31469](https://togithub.com/hashicorp/terraform/issues/31469)) ### [`v1.2.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.5...v1.2.6) #### 1.2.6 (July 27, 2022) ENHANCEMENTS: - Add a warning and guidance when `terraform init` fails to fully populate the `.terraform.lock.hcl` file. ([#31399](https://togithub.com/hashicorp/terraform/issues/31399)) - Add a direct link to the relevant documentation when `terraform init` fails on missing checksums. ([#31408](https://togithub.com/hashicorp/terraform/issues/31408)) BUG FIXES: - Fix panic on `terraform show` when state file is invalid or unavailable. ([#31444](https://togithub.com/hashicorp/terraform/issues/31444)) - Fix `terraform providers lock` command failing on missing checksums. ([#31389](https://togithub.com/hashicorp/terraform/issues/31389)) - Some combinations of move block operations would be executed in the wrong order ([#31499](https://togithub.com/hashicorp/terraform/issues/31499)) - Don't attribute an error to the provider when a computed attribute is listed in `ignore_changes` ([#31509](https://togithub.com/hashicorp/terraform/issues/31509)) ### [`v1.2.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.4...v1.2.5) #### 1.2.5 (July 13, 2022) BUG FIXES: - Report correct error message when a prerelease field is included in the `required_version` global constraint. ([#31331](https://togithub.com/hashicorp/terraform/issues/31331)) - Fix case when extra blank lines were inserted into the plan for unchanged blocks. ([#31330](https://togithub.com/hashicorp/terraform/issues/31330)) ### [`v1.2.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.3...v1.2.4) #### 1.2.4 (June 29, 2022) ENHANCEMENTS: - Improved validation of `required_providers` to prevent single providers from being required with multiple names. ([#31218](https://togithub.com/hashicorp/terraform/issues/31218)) - Improved plan performance by optimizing `addrs.Module.String` for allocations. ([#31293](https://togithub.com/hashicorp/terraform/issues/31293)) BUG FIXES: - backend/http: Fixed bug where the HTTP backend would fail to retry acquiring the state lock and ignored the `-lock-timeout` flag. ([#31256](https://togithub.com/hashicorp/terraform/issues/31256)) - Fix crash if a `precondition` or `postcondition` block omitted the required `condition` argument. ([#31290](https://togithub.com/hashicorp/terraform/issues/31290)) ### [`v1.2.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.2...v1.2.3) #### 1.2.3 (June 15, 2022) UPGRADE NOTES: - The following remote state backends are now marked as deprecated, and are planned to be removed in a future Terraform release. These backends have been unmaintained since before Terraform v1.0, and may contain known bugs, outdated packages, or security vulnerabilities. - artifactory - etcd - etcdv3 - manta - swift BUG FIXES: - Missing check for error diagnostics in GetProviderSchema could result in panic ([#31184](https://togithub.com/hashicorp/terraform/issues/31184)) - Module registries returning X-Terraform-Get locations with no URL would error with "no getter available for X-Terraform-Get source protocol" ([#31237](https://togithub.com/hashicorp/terraform/issues/31237)) - Fix crash from concurrent operation on shared set of resource instance dependencies ([#31246](https://togithub.com/hashicorp/terraform/issues/31246)) - backend/cos: `tencentcloud-terraform-lock` tag was not removed in all cases ([#31223](https://togithub.com/hashicorp/terraform/issues/31223)) ### [`v1.2.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.1...v1.2.2) #### 1.2.2 (June 01, 2022) ENHANCEMENTS: - Invalid `-var` arguments with spaces between the name and value now have an improved error message ([#30985](https://togithub.com/hashicorp/terraform/issues/30985)) BUG FIXES: - Terraform now hides invalid input values for sensitive root module variables when generating error diagnostics ([#30552](https://togithub.com/hashicorp/terraform/issues/30552)) - Fixed crash on CLI autocomplete ([#31160](https://togithub.com/hashicorp/terraform/issues/31160)) - The "Configuration contains unknown values" error message now includes attribute paths ([#31111](https://togithub.com/hashicorp/terraform/issues/31111)) ### [`v1.2.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.0...v1.2.1) #### 1.2.1 (May 23, 2022) BUG FIXES: - SSH provisioner connections fail when using signed `ed25519` keys ([#31092](https://togithub.com/hashicorp/terraform/issues/31092)) - Crash with invalid module source ([#31060](https://togithub.com/hashicorp/terraform/issues/31060)) - Incorrect "Module is incompatible with count, for_each, and depends_on" error when a provider is nested within a module along with a sub-module using `count` or `for_each` ([#31091](https://togithub.com/hashicorp/terraform/issues/31091)) ### [`v1.2.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.9...v1.2.0) #### 1.2.0 (May 18, 2022) UPGRADE NOTES: - If you use the [third-party credentials helper plugin terraform-credentials-env](https://togithub.com/apparentlymart/terraform-credentials-env), you should disable it as part of upgrading to Terraform v1.2 because similar functionality is now built in to Terraform itself. The new behavior supports the same environment variable naming scheme but has a difference in priority order from the credentials helper: `TF_TOKEN_...` environment variables will now take priority over credentials blocks in CLI configuration and credentials stored automatically by terraform login, which is not true for credentials provided by any credentials helper plugin. If you see Terraform using different credentials after upgrading, check to make sure you do not specify credentials for the same host in multiple locations. If you use the credentials helper in conjunction with the [hashicorp/tfe](https://registry.terraform.io/providers/hashicorp/tfe) Terraform provider to manage Terraform Cloud or Terraform Enterprise objects with Terraform, you should also upgrade to version 0.31 of that provider, which added the corresponding built-in support for these environment variables. - The official Linux packages for the v1.2 series now require Linux kernel version 2.6.32 or later. - When making outgoing HTTPS or other TLS connections as a client, Terraform now requires the server to support TLS v1.2. TLS v1.0 and v1.1 are no longer supported. Any safely up-to-date server should support TLS 1.2, and mainstream web browsers have required it since 2020. - When making outgoing HTTPS or other TLS connections as a client, Terraform will no longer accept CA certificates signed using the SHA-1 hash function. Publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015. (Note: the changes to Terraform's requirements when interacting with TLS servers apply only to requests made by Terraform CLI itself, such as provider/module installation and state storage requests. Terraform provider plugins include their own TLS clients which may have different requirements, and may add new requirements in their own releases, independently of Terraform CLI changes.) NEW FEATURES: - `precondition` and `postcondition` check blocks for resources, data sources, and module output values: module authors can now document assumptions and assertions about configuration and state values. If these conditions are not met, Terraform will report a custom error message to the user and halt further execution. - `replace_triggered_by` is a new `lifecycle` argument for managed resources which triggers replacement of an object based on changes to an upstream dependency. - You can now specify credentials for [Terraform-native services](https://www.terraform.io/internals/remote-service-discovery) using an environment variable named as `TF_TOKEN_` followed by an encoded version of the hostname. For example, Terraform will use variable `TF_TOKEN_app_terraform_io` as a bearer token for requests to "app.terraform.io", for the Terraform Cloud integration and private registry requests. ENHANCEMENTS: - When showing a plan, Terraform CLI will now only show "Changes outside of Terraform" if they relate to resources and resource attributes that contributed to the changes Terraform is proposing to make. ([#30486](https://togithub.com/hashicorp/terraform/issues/30486)) - Error messages for preconditions, postconditions, and custom variable validations are now evaluated as expressions, allowing interpolation of relevant values into the output. ([#30613](https://togithub.com/hashicorp/terraform/issues/30613)) - When showing the progress of a remote operation running in Terraform Cloud, Terraform CLI will include information about post-plan [run tasks](https://www.terraform.io/cloud-docs/workspaces/settings/run-tasks). ([#30141](https://togithub.com/hashicorp/terraform/issues/30141)) - Terraform will now show a slightly different note in the plan output if a data resource read is deferred to the apply step due to it depending on a managed resource that has changes pending. ([#30971](https://togithub.com/hashicorp/terraform/issues/30971)) - The "Invalid for_each argument" error message for unknown maps/sets now includes an additional paragraph to try to help the user notice they can move apply-time values into the map *values* instead of the map *keys*, and thus avoid the problem without resorting to `-target`. ([#30327](https://togithub.com/hashicorp/terraform/issues/30327)) - There are some small improvements to the error and warning messages Terraform will emit in the case of invalid provider configuration passing between modules. There are no changes to which situations will produce errors and warnings, but the messages now include additional information intended to clarify what problem Terraform is describing and how to address it. ([#30639](https://togithub.com/hashicorp/terraform/issues/30639)) - The environment variables `TF_CLOUD_ORGANIZATION` and `TF_CLOUD_HOSTNAME` now serve as fallbacks for the arguments of the same name inside a `cloud` block configuring integration with Terraform Cloud. - The environment variable `TF_WORKSPACE` will now additionally serve as an implicit configuration of a single selected workspace on Terraform Cloud if (and only if) the `cloud` block does not include an explicit workspaces configuration. - The AzureRM Backend now defaults to using MSAL (and Microsoft Graph) rather than ADAL (and Azure Active Directory Graph) for authentication. ([#30891](https://togithub.com/hashicorp/terraform/issues/30891)) - The AzureRM Backend now supports authenticating as a service principal using OpenID Connect. ([#30936](https://togithub.com/hashicorp/terraform/pull/30936)) - When running on macOS, Terraform will now use platform APIs to validate certificates presented by TLS (HTTPS) servers. This may change exactly which root certificates Terraform will accept as valid. ([#30768](https://togithub.com/hashicorp/terraform/issues/30768)) - Show remote host in error message for clarity when installation of provider fails ([#30810](https://togithub.com/hashicorp/terraform/issues/30810)) - Terraform now prints a warning when adding an attribute to `ignore_changes` that is managed only by the provider. Specifying non-configurable attributes in `ignore_changes` has no effect because `ignore_changes` tells Terraform to ignore future changes made in the configuration. ([#30517](https://togithub.com/hashicorp/terraform/issues/30517)) - `terraform show -json` now includes exact type information for output values. ([#30945](https://togithub.com/hashicorp/terraform/issues/30945)) - The `ssh` provisioner connection now supports SSH over HTTP proxy. ([#30274](https://togithub.com/hashicorp/terraform/pull/30274)) - - The SSH client for provisioners now supports newer key algorithms, allowing it to connect to servers running more recent versions of OpenSSH. ([#30962](https://togithub.com/hashicorp/terraform/issues/30962)) BUG FIXES: - Terraform now handles type constraints, nullability, and custom variable validation properly for root module variables. Previously there was an order of operations problem where the nullability and custom variable validation were checked too early, prior to dealing with the type constraints, and thus that logic could potentially "see" an incorrectly-typed value in spite of the type constraint, leading to incorrect errors. ([#29959](https://togithub.com/hashicorp/terraform/issues/29959)) - When reporting a type mismatch between the true and false results of a conditional expression when both results are of the same structural type kind (object/tuple, or a collection thereof), Terraform will no longer return a confusing message like "the types are object and object, respectively", and will instead attempt to explain how the two structural types differ. ([#30920](https://togithub.com/hashicorp/terraform/issues/30920)) - Applying the various type conversion functions like `tostring`, `tonumber`, etc to `null` will now return a null value of the intended type. For example, `tostring(null)` converts from a null value of an unknown type to a null value of string type. Terraform can often handle such conversions automatically when needed, but explicit annotations like this can help Terraform to understand author intent when inferring type conversions for complex-typed values. ([#30879](https://togithub.com/hashicorp/terraform/issues/30879)) - Terraform now returns an error when `cidrnetmask()` is called with an IPv6 address, as it was previously documented to do. IPv6 standards do not preserve the "netmask" syntax sometimes used for IPv4 network configuration; use CIDR prefix syntax instead. ([#30703](https://togithub.com/hashicorp/terraform/issues/30703)) - When performing advanced state management with the `terraform state` commands, Terraform now checks the `required_version` field in the configuration before proceeding. ([#30511](https://togithub.com/hashicorp/terraform/pull/30511)) - When rendering a diff, Terraform now quotes the name of any object attribute whose string representation is not a valid identifier. ([#30766](https://togithub.com/hashicorp/terraform/issues/30766)) - Terraform will now prioritize local terraform variables over remote terraform variables in operations such as `import`, `plan`, `refresh` and `apply` for workspaces in local execution mode. This behavior applies to both `remote` backend and the `cloud` integration configuration. ([#29972](https://togithub.com/hashicorp/terraform/issues/29972)) - `terraform show -json`: JSON plan output now correctly maps aliased providers to their configurations, and includes the full provider source address alongside the short provider name. ([#30138](https://togithub.com/hashicorp/terraform/issues/30138)) - The local token configuration in the `cloud` and `remote` backend now has higher priority than a token specified in a `credentials` block in the CLI configuration. ([#30664](https://togithub.com/hashicorp/terraform/issues/30664)) - The `cloud` integration now gracefully exits when `-input=false` and an operation requires some user input. - Terraform will now reliably detect an inteerruptiong (e.g. Ctrl+C) during planning for `terraform apply -auto-approve`. Previously there was a window of time where interruption would cancel the plan step but not prevent Terraform from proceeding to the apply step. ([#30979](https://togithub.com/hashicorp/terraform/issues/30979)) - Terraform will no longer crash if a provider fails to return a schema. ([#30987](https://togithub.com/hashicorp/terraform/issues/30987)) ### [`v1.1.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.8...v1.1.9) #### 1.1.9 (April 20, 2022) BUG FIXES: - cli: Fix crash when using sensitive values in sets. ([#30825](https://togithub.com/hashicorp/terraform/issues/30825)) - cli: Fix double-quoted map keys when rendering a diff. ([#30855](https://togithub.com/hashicorp/terraform/issues/30855)) - core: Prevent errors when handling a data source with incompatible schema changes ([#30830](https://togithub.com/hashicorp/terraform/issues/30830)) ENHANCEMENTS: - cli: Terraform now supports [run tasks](https://www.terraform.io/cloud-docs/workspaces/settings/run-tasks), a Terraform Cloud integration for executing remote operations, for the post plan stage of a run. ### [`v1.1.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.7...v1.1.8) #### 1.1.8 (April 07, 2022) BUG FIXES: - cli: Fix missing identifying attributes (e.g. "id", "name") when displaying plan diffs with nested objects. ([#30685](https://togithub.com/hashicorp/terraform/issues/30685)) - functions: Fix error when `sum()` function is called with a collection of string-encoded numbers, such as `sum(["1", "2", "3"])`. ([#30684](https://togithub.com/hashicorp/terraform/issues/30684)) - When rendering a diff, Terraform now quotes the name of any object attribute whose string representation is not a valid identifier. ([#30766](https://togithub.com/hashicorp/terraform/issues/30766)) - Terraform will no longer crash in the `terraform apply` phase if an error occurs during backend configuration. ([#30780](https://togithub.com/hashicorp/terraform/pull/30780)) ### [`v1.1.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.6...v1.1.7) #### 1.1.7 (March 02, 2022) BUG FIXES: - `terraform show -json`: Improve performance for deeply-nested object values. The previous implementation was accidentally quadratic, which could result in very long execution time for generating JSON plans, and timeouts on Terraform Cloud and Terraform Enterprise. ([#30561](https://togithub.com/hashicorp/terraform/issues/30561)) - cloud: Update go-slug for terraform.tfstate exclusion to prevent a user from getting an error after migrating state to TFC. ### [`v1.1.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.5...v1.1.6) #### 1.1.6 (February 16, 2022) BUG FIXES: - cli: Prevent complex uses of the console-only `type` function. This function may only be used at the top level of console expressions, to display the type of a given value. Attempting to use this function in complex expressions will now display a diagnostic error instead of crashing. ([#30476](https://togithub.com/hashicorp/terraform/issues/30476)) - `terraform state mv`: Will now correctly exit with error code `1` when the specified resources cannot be found in state. Previously Terraform would display appropriate diagnostic errors, but exit successfully. ([#29365](https://togithub.com/hashicorp/terraform/issues/29365)) ### [`v1.1.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.4...v1.1.5) #### 1.1.5 (February 02, 2022) ENHANCEMENTS: - backend/s3: Update AWS SDK to allow the use of the ap-southeast-3 region ([#30363](https://togithub.com/hashicorp/terraform/issues/30363)) BUG FIXES: - cli: Fix crash when using autocomplete with long commands, such as `terraform workspace select` ([#30193](https://togithub.com/hashicorp/terraform/issues/30193)) ### [`v1.1.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.3...v1.1.4) #### 1.1.4 (January 19, 2022) BUG FIXES: - config: Non-nullable variables with null inputs were not given default values when checking validation statements ([#30330](https://togithub.com/hashicorp/terraform/issues/30330)) - config: Terraform will no longer incorrectly report "Cross-package move statement" when an external package has changed a resource from no `count` to using `count`, or vice-versa. ([#30333](https://togithub.com/hashicorp/terraform/issues/30333)) ### [`v1.1.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.2...v1.1.3) #### 1.1.3 (January 06, 2022) BUG FIXES: - `terraform init`: Will now remove from [the dependency lock file](https://www.terraform.io/language/files/dependency-lock) entries for providers not used in the current configuration. Previously it would leave formerly-used providers behind in the lock file, leading to "missing or corrupted provider plugins" errors when other commands verified the consistency of the installed plugins against the locked plugins. ([#30192](https://togithub.com/hashicorp/terraform/issues/30192)) - config: Fix panic when encountering an invalid provider block within a module ([#30095](https://togithub.com/hashicorp/terraform/issues/30095)) - config: Fix cycle error when the index of a module containing move statements is changed ([#30232](https://togithub.com/hashicorp/terraform/issues/30232)) - config: Fix inconsistent ordering with nested move operations ([#30253](https://togithub.com/hashicorp/terraform/issues/30253)) - config: Fix `moved` block refactoring to include nested modules ([#30233](https://togithub.com/hashicorp/terraform/issues/30233)) - functions: Redact sensitive values from function call error messages ([#30067](https://togithub.com/hashicorp/terraform/issues/30067)) - `terraform show`: Disable plan state lineage checks, ensuring that we can show plan files which were generated against non-default state files ([#30205](https://togithub.com/hashicorp/terraform/issues/30205)) ### [`v1.1.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.1...v1.1.2) #### 1.1.2 (December 17, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to this new version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. BUG FIXES: - config: Fix panic when using `-target` in combination with `moved` blocks within modules ([#30189](https://togithub.com/hashicorp/terraform/issues/30189)) - core: Fix condition which could lead to an empty state being written when there is a failure building the apply graph ([#30199](https://togithub.com/hashicorp/terraform/issues/30199)) ### [`v1.1.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.0...v1.1.1) #### 1.1.1 (December 15, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to the latest version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. *** BUG FIXES: - core: Fix crash with orphaned module instance due to changed `count` or `for_each` value ([#30151](https://togithub.com/hashicorp/terraform/issues/30151)) - core: Fix regression where some expressions failed during validation when referencing resources expanded with `count` or `for_each` ([#30171](https://togithub.com/hashicorp/terraform/issues/30171)) ### [`v1.1.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.11...v1.1.0) #### 1.1.0 (December 08, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to the latest version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. *** Terraform v1.1.0 is a new minor release, containing some new features and some bug fixes whose scope was too large for inclusion in a patch release. NEW FEATURES: - `moved` blocks for refactoring within modules: Module authors can now record in module source code whenever they've changed the address of a resource or resource instance, and then during planning Terraform will automatically migrate existing objects in the state to new addresses. This therefore avoids the need for users of a shared module to manually run `terraform state mv` after upgrading to a version of the module, as long as the change is expressible as static configuration. However, `terraform state mv` will remain available for use in more complex migration situations that are not well-suited to declarative configuration. - A new `cloud` block in the `terraform` settings block introduces a native Terraform Cloud integration for the [CLI-driven run workflow](https://www.terraform.io/docs/cloud/run/cli.html). The Cloud integration includes several enhancements, including per-run variable support using the `-var` flag, the ability to map Terraform Cloud workspaces to the current configuration via [Workspace Tags](https://www.terraform.io/docs/cloud/api/workspaces.html#get-tags), and an improved user experience for Terraform Cloud and Enterprise users with actionable error messages and prompts. - `terraform plan` and `terraform apply` both now include additional annotations for resource instances planned for deletion to explain why Terraform has proposed that action. For example, if you change the `count` argument for a resource to a lower number then Terraform will now mention that as part of proposing to destroy any existing objects that exceed the new count. UPGRADE NOTES: This release is covered by the [Terraform v1.0 Compatibility Promises](https://www.terraform.io/docs/language/v1-compatibility-promises.html), but does include some changes permitted within those promises as described below. - Terraform on macOS now requires macOS 10.13 High Sierra or later; Older macOS versions are no longer supported. - The `terraform graph` command no longer supports `-type=validate` and `-type=eval` options. The validate graph is always the same as the plan graph anyway, and the "eval" graph was just an implementation detail of the `terraform console` command. The default behavior of creating a plan graph should be a reasonable replacement for both of the removed graph modes. (Please note that `terraform graph` is not covered by the Terraform v1.0 compatibility promises, because its behavior inherently exposes Terraform Core implementation details, so we recommend it only for interactive debugging tasks and not for use in automation.) - `terraform apply` with a previously-saved plan file will now verify that the provider plugin packages used to create the plan fully match the ones used during apply, using the same checksum scheme that Terraform normally uses for the dependency lock file. Previously Terraform was checking consistency of plugins from a plan file using a legacy mechanism which covered only the main plugin executable, not any other files that might be distributed alongside in the plugin package. This additional check should not affect typical plugins that conform to the expectation that a plugin package's contents are immutable once released, but may affect a hypothetical in-house plugin that intentionally modifies extra files in its package directory somehow between plan and apply. If you have such a plugin, you'll need to change its approach to store those files in some other location separate from the package directory. This is a minor compatibility break motivated by increasing the assurance that plugins have not been inadvertently or maliciously modified between plan and apply. - `terraform state mv` will now error when legacy `-backup` or `-backup-out` options are used without the `-state` option on non-local backends. These options operate on a local state file only. Previously, these options were accepted but ignored silently when used with non-local backends. - In the AzureRM backend, the new opt-in option `use_microsoft_graph` switches to using MSAL authentication tokens and Microsoft Graph rather than using ADAL tokens and Azure Active Directory Graph, which is now [deprecated by Microsoft](https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq). The new mode will become the default in Terraform v1.2, so please plan to migrate to using this setting and test with your own Azure AD tenant prior to the Terraform v1.2 release. ENHANCEMENTS: - config: Terraform now checks the syntax of and normalizes module source addresses (the `source` argument in `module` blocks) during configuration decoding rather than only at module installation time. This is largely just an internal refactoring, but a visible benefit of this change is that the `terraform init` messages about module downloading will now show the canonical module package address Terraform is downloading from, after interpreting the special shorthands for common cases like GitHub URLs. ([#28854](https://togithub.com/hashicorp/terraform/issues/28854)) - config: Variables can now be declared as "nullable", which defines whether a variable can be null within a module. Setting `nullable = false` ensures that a variable value will never be `null`, and may instead take on the variable's default value if the caller sets it explicitly to `null`. ([#29832](https://togithub.com/hashicorp/terraform/issues/29832)) - `terraform plan` and `terraform apply`: When Terraform plans to destroy a resource instance due to it no longer being declared in the configuration, the proposed plan output will now include a note hinting at what situation prompted that proposal, so you can more easily see what configuration change might avoid the object being destroyed. ([#29637](https://togithub.com/hashicorp/terraform/pull/29637)) - `terraform plan` and `terraform apply`: Terraform will now report explicitly in the UI if it automatically moves a resource instance to a new address as a result of adding or removing the `count` argument from an existing resource. For example, if you previously had `resource "aws_subnet" "example"` *without* `count`, you might have `aws_subnet.example` already bound to a remote object in your state. If you add `count = 1` to that resource then Terraform would previously silently rebind the object to `aws_subnet.example[0]` as part of planning, whereas now Terraform will mention that it did so explicitly in the plan description. ([#29605](https://togithub.com/hashicorp/terraform/issues/29605)) - `terraform workspace delete`: will now allow deleting a workspace whose state contains only data resource instances and output values, without running `terraform destroy` first. Previously the presence of data resources would require using `-force` to override the safety check guarding against accidentally forgetting about remote objects, but a data resource is not responsible for the management of its associated remote object(s) and so there's no reason to require explicit deletion. ([#29754](https://togithub.com/hashicorp/terraform/issues/29754)) - `terraform validate`: Terraform now uses precise type information for resources during config validation, allowing more problems to be caught that that step rather than only during the planning step. ([#29862](https://togithub.com/hashicorp/terraform/issues/29862)) - provisioner/remote-exec and provisioner/file: When using SSH agent authentication mode on Windows, Terraform can now detect and use [the Windows 10 built-in OpenSSH Client](https://devblogs.microsoft.com/powershell/using-the-openssh-beta-in-windows-10-fall-creators-update-and-windows-server-1709/)'s SSH Agent, when available, in addition to the existing support for the third-party solution [Pageant](https://documentation.help/PuTTY/pageant.html) that was already supported. ([#29747](https://togithub.com/hashicorp/terraform/issues/29747)) - cli: `terraform state mv` will now return an error for `-backup` or `-backup-out` options used without the `-state` option, unless the working directory is initialized to use the local backend. Previously Terraform would silently ignore those options, since they are applicable only to the local backend. ([#27908](https://togithub.com/hashicorp/terraform/issues/27908)) - `terraform console`: now has a new `type()` function, available only in the interactive console, for inspecting the exact type of a particular value as an aid to debugging. ([#28501](https://togithub.com/hashicorp/terraform/issues/28501)) BUG FIXES: - config: `ignore_changes = all` now works in override files. ([#29849](https://togithub.com/hashicorp/terraform/issues/29849)) - config: Upgrading an unknown single value to a list using a splat expression now correctly returns an unknown value and type. Previously it would sometimes "overpromise" a particular return type, leading to an inconsistency error during the apply step. ([#30062](https://togithub.com/hashicorp/terraform/issues/30062)) - config: Terraform is now more precise in its detection of data resources that must be deferred to the apply step due to their `depends_on` arguments referring to not-yet-converged managed resources. ([#29682](https://togithub.com/hashicorp/terraform/issues/29682)) - config: `ignore_changes` can no longer cause a null map to be converted to an empty map, which would otherwise potentially cause surprising side-effects in provider logic. ([#29928](https://togithub.com/hashicorp/terraform/issues/29928)) - core: Provider configuration obtained from interactive prompts will now be merged properly with settings given in the configuration. Previously this merging was incorrect in some cases. ([#29000](https://togithub.com/hashicorp/terraform/issues/29000)) - `terraform plan`: Improved rendering of changes inside attributes that accept lists, sets, or maps of nested object types. ([#29827](https://togithub.com/hashicorp/terraform/issues/29827), [#29983](https://togithub.com/hashicorp/terraform/issues/29983), [#29986](https://togithub.com/terraform/issues/29986)) - `terraform apply`: Will no longer try to apply a stale plan that was generated against an originally-empty state. Previously this was an unintended exception to the rule that a plan can only be applied to the state snapshot it was generated against. ([#29755](https://togithub.com/hashicorp/terraform/issues/29755)) - `terraform show -json`: Attributes that are declared as using the legacy [Attributes as Blocks](https://www.terraform.io/docs/language/attr-as-blocks.html) behavior are now represented more faithfully in the JSON plan output. ([#29522](https://togithub.com/hashicorp/terraform/issues/29522)) - `terraform init`: Will now update the backend configuration hash value at a more approprimate time, to ensure properly restarting a backend migration process that failed on the first attempt. ([#29860](https://togithub.com/hashicorp/terraform/issues/29860)) - backend/oss: Flatten `assume_role` block arguments, so that they are more compatible with the `terraform_remote_state` data source. ([#29307](https://togithub.com/hashicorp/terraform/issues/29307)) ### [`v1.0.11`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.11) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.10...v1.0.11) #### 1.0.11 (November 10, 2021) ENHANCEMENTS: - backend/oss: Added support for `sts_endpoint` ([#29841](https://togithub.com/hashicorp/terraform/issues/29841)) BUG FIXES: - config: Fixed a bug in which `ignore_changes = all` would not work in override files ([#29849](https://togithub.com/hashicorp/terraform/issues/29849)) - config: Numbers are now compared for equality based on their protocol representation, eliminating unexpected changes due to small precision errors ([#29864](https://togithub.com/hashicorp/terraform/issues/29864)) ### [`v1.0.10`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.10) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.9...v1.0.10) #### 1.0.10 (October 28, 2021) BUG FIXES: - backend/oss: Fix panic when there's an error looking up OSS endpoints ([#29784](https://togithub.com/hashicorp/terraform/issues/29784)) - backend/remote: Fix version check when migrating state ([#29793](https://togithub.com/hashicorp/terraform/issues/29793)) - cli: Restore `-lock` and `-lock-timeout` flags for the `init` command, which were removed in 0.15.0 ([#29773](https://togithub.com/hashicorp/terraform/issues/29773)) - cli: Fix bug where `terraform init -input=false` would hang waiting for user input to choose a workspace ([#29805](https://togithub.com/hashicorp/terraform/issues/29805)) ### [`v1.0.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.8...v1.0.9) #### 1.0.9 (October 13, 2021) BUG FIXES: - core: Fix panic when planning new resources with nested object attributes ([#29701](https://togithub.com/hashicorp/terraform/issues/29701)) - core: Do not refresh deposed instances when the provider is not configured during destroy ([#29720](https://togithub.com/hashicorp/terraform/issues/29720)) - core: Prevent panic when encountering a missing change when destroying a resource ([#29734](https://togithub.com/hashicorp/terraform/issues/29734)) ### [`v1.0.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.7...v1.0.8) #### 1.0.8 (September 29, 2021) BUG FIXES: - cli: Check `required_version` as early as possibly during `init` so that version incompatibility can be reported before errors about new syntax ([#29665](https://togithub.com/hashicorp/terraform/issues/29665)) - core: Don't plan to remove orphaned resource instances in refresh-only plans ([#29640](https://togithub.com/hashicorp/terraform/issues/29640)) ### [`v1.0.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.6...v1.0.7) #### 1.0.7 (September 15, 2021) BUG FIXES: - core: Remove check for computed attributes which is no longer valid with optional structural attributes ([#29563](https://togithub.com/hashicorp/terraform/issues/29563)) - core: Prevent object types with optional attributes from being instantiated as concrete values, which can lead to failures in type comparison ([#29559](https://togithub.com/hashicorp/terraform/issues/29559)) - core: Empty containers in the configuration were not planned correctly when used with optional structural attributes ([#29580](https://togithub.com/hashicorp/terraform/issues/29580)) ### [`v1.0.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.5...v1.0.6) #### 1.0.6 (September 03, 2021) ENHANCEMENTS: - backend/s3: Improve SSO handling and add new endpoints in the AWS SDK ([#29017](https://togithub.com/hashicorp/terraform/issues/29017)) BUG FIXES: - cli: Suppress confirmation prompt when initializing with the `-force-copy` flag and migrating state between multiple workspaces. ([#29438](https://togithub.com/hashicorp/terraform/issues/29438)) - cli: Update tencentcount dependency versions to fix errors when building from source ([#29445](https://togithub.com/hashicorp/terraform/issues/29445)) - core: Fix panic while handling computed attributes within nested objects, and improve plan validation for unknown values ([#29482](https://togithub.com/hashicorp/terraform/issues/29482)) ### [`v1.0.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.4...v1.0.5) #### 1.0.5 (August 18, 2021) BUG FIXES: - json-output: Add an output change summary message as part of the `terraform plan -json` structured logs, bringing this format into parity with the human-readable UI. ([#29312](https://togithub.com/hashicorp/terraform/issues/29312)) - core: Handle null nested single attribute values ([#29411](https://togithub.com/hashicorp/terraform/issues/29411)) - cli: Fix crash when planning a diff between null and empty sets in nested attributes ([#29398](https://togithub.com/hashicorp/terraform/issues/29398)) - cli: Fix crash when planning a new resource containing a set of nested object attributes ([#29398](https://togithub.com/hashicorp/terraform/issues/29398)) - cli: Fix crash when displaying a resource diff where a possibly identifying attribute is sensitive ([#29397](https://togithub.com/hashicorp/terraform/issues/29397)) - cli: Fix crash when a diff with unknown nested map attributes ([#29410](https://togithub.com/hashicorp/terraform/issues/29410)) - config: Fix handling of dynamically types arguments in `formatlist`, ensuring the correct resulting type. ([#29408](https://togithub.com/hashicorp/terraform/issues/29408)) - config: Floating point operations like `floor` and `ceil` can no longer mutate their arguments. ([#29408](https://togithub.com/hashicorp/terraform/issues/29408)) ### [`v1.0.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.3...v1.0.4) #### 1.0.4 (August 04, 2021) BUG FIXES: - backend/consul: Fix a bug where the state value may be too large for consul to accept ([#28838](https://togithub.com/hashicorp/terraform/issues/28838)) - cli: Fixed a crashing bug with some edge-cases when reporting syntax errors that happen to be reported at the position of a newline. ([#29048](https://togithub.com/hashicorp/terraform/issues/29048)) ### [`v1.0.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.2...v1.0.3) #### 1.0.3 (July 21, 2021) ENHANCEMENTS - `terraform plan`: The JSON logs (`-json` option) will now include `resource_drift`, showing changes detected outside of Terraform during the refresh step. ([#29072](https://togithub.com/hashicorp/terraform/issues/29072)) - core: The automatic provider installer will now accept providers that are recorded in their registry as using provider protocol version 6. ([#29153](https://togithub.com/hashicorp/terraform/issues/29153)) - backend/etcdv3: New argument `max_request_bytes` allows larger requests and for the client, to match the server request limit. ([#28078](https://togithub.com/hashicorp/terraform/issues/28078)) BUG FIXES: - `terraform plan`: Will no longer panic when trying to render null maps. ([#29207](https://togithub.com/hashicorp/terraform/issues/29207)) - backend/pg: Prevent the creation of multiple workspaces with the same name. ([#29157](https://togithub.com/hashicorp/terraform/issues/29157)) - backend/oss: STS auth is now supported. ([#29167](https://togithub.com/hashicorp/terraform/issues/29167)) - config: Dynamic blocks with unknown for_each values were not being validated. Ensure block attributes are valid even when the block is unknown ([#29208](https://togithub.com/hashicorp/terraform/issues/29208)) - config: Unknown values in string templates could lose sensitivity, causing the planned change to be inaccurate ([#29208](https://togithub.com/hashicorp/terraform/issues/29208)) ### [`v1.0.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.1...v1.0.2) #### 1.0.2 (July 07, 2021) BUG FIXES: - `terraform show`: Fix crash when rendering JSON plan with sensitive values in state ([#29049](https://togithub.com/hashicorp/terraform/issues/29049)) - config: The `floor` and `ceil` functions no longer lower the precision of arguments to what would fit inside a 64-bit float, instead preserving precision in a similar way as most other arithmetic functions. ([#29110](https://togithub.com/hashicorp/terraform/issues/29110)) - config: The `flatten` function was incorrectly treating null values of an unknown type as if they were unknown values. Now it will treat them the same as any other non-list/non-tuple value, flattening them down into the result as-is. ([#29110](https://togithub.com/hashicorp/terraform/issues/29110)) ### [`v1.0.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.0...v1.0.1) #### 1.0.1 (June 24, 2021) ENHANCEMENTS: - json-output: The JSON plan output now indicates which state values are sensitive. ([#28889](https://togithub.com/hashicorp/terraform/issues/28889)) - cli: The darwin builds can now make use of the host DNS resolver, which will fix many network related issues on MacOS. BUG FIXES: - backend/remote: Fix faulty Terraform Cloud version check when migrating state to the remote backend with multiple local workspaces ([#28864](https://togithub.com/hashicorp/terraform/issues/28864)) - cli: Fix crash with deposed instances in json plan output ([#28922](https://togithub.com/hashicorp/terraform/issues/28922)) - core: Fix crash when provider modifies and unknown block during plan ([#28941](https://togithub.com/hashicorp/terraform/issues/28941)) - core: Diagnostic context was missing for some errors when validating blocks ([#28979](https://togithub.com/hashicorp/terraform/issues/28979)) - core: Fix crash when calling `setproduct` with unknown values ([#28984](https://togithub.com/hashicorp/terraform/issues/28984)) - json-output: Fix an issue where the JSON configuration representation was missing fully-unwrapped references. ([#28884](https://togithub.com/hashicorp/terraform/issues/28884)) - json-output: Fix JSON plan resource drift to remove unchanged resources. ([#28975](https://togithub.com/hashicorp/terraform/issues/28975)) ### [`v1.0.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.15.5...v1.0.0) #### 1.0.0 (June 08, 2021) Terraform v1.0 is an unusual release in that its primary focus is on stability, and it represents the culmination of several years of work in previous major releases to make sure that the Terraform language and internal architecture will be a suitable foundation for forthcoming additions that will remain backward compatible. Terraform v1.0.0 intentionally has no significant changes compared to Terraform v0.15.5. You can consider the v1.0 series as a direct continuation of the v0.15 series; we do not intend to issue any further releases in the v0.15 series, because all of the v1.0 releases will be only minor updates to address bugs. For all future minor releases with major version 1, we intend to preserve backward compatibility as described in detail in [the Terraform v1.0 Compatibility Promises](https://www.terraform.io/docs/language/v1-compatibility-promises.html). The later Terraform v1.1.0 will, therefore, be the first minor release with new features that we will implement with consideration of those promises. ### [`v0.15.5`](https://togithub.com/hashicorp/terraform/releases/tag/v0.15.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.15.4...v0.15.5) #### 0.15.5 (June 02, 2021) BUG FIXES: - `terraform plan` and `terraform apply`: Don't show "Objects have changed" notification when the detected changes are only internal details related to legacy SDK quirks. ([#28796](https://togithub.com/hashicorp/terraform/issues/28796)) - core: Prevent crash during planning when encountering a deposed instance that has been removed from the configuration. ([#28766](https://togithub.com/hashicorp/terraform/issues/28766)) - core: Fix crash when rendering changes to deposed instances outside of Terraform. ([#28796](https://togithub.com/hashicorp/terraform/issues/28796)) - core: Restore a missing error when attempting to import a non-existent remote object. ([#28808](https://togithub.com/hashicorp/terraform/issues/28808)) - core: Fix bug where Terraform failed to release the state lock when applying a stale saved plan failed. ([#28819](https://togithub.com/hashicorp/terraform/issues/28819)) ### [`v0.15.4`](https://togithub.com/hashicorp/terraform/releases/tag/v0.15.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.15.3...v0.15.4) #### 0.15.4 (May 19, 2021) NEW FEATURES: - **Noting changes made outside of Terraform:** Terraform has always, by default, made a point during the planning operation of reading the current state of remote objects in order to detect any changes made outside of Terraform, to make sure the plan will take those into account. Terraform will now report those detected changes as part of the plan result, in order to give additional context about the planned changes. We've often heard that people find it confusing when a plan includes a change that doesn't seem to be prompted by any recent change in the *configuration*, and so this feature is aiming to provide the previously-missing explanation for situations where Terraform is planning to undo a change. It can also be useful just as general information when the change *won't* be undone by Terraform: if you've intentionally made a change outside of Terraform and mirrored that change in your configuration then Terraform will now confirm that it noticed the change you made and took it into account when planning. By default this new output is for information only and doesn't change any behavior. If Terraform detects a change you were *expecting* then you don't need to take any additional action to respond to it. However, we've also added a new planning mode `-refresh-only` which allows you to explicitly plan and apply the action of writing those detected changes to the Terraform state, which serves as a plannable replacement for `terraform refresh`. We don't have any plans to remove the long-standing `terraform refresh` command, but we do recommend using `terraform apply -refresh-only` instead in most cases, because it will provide an opportunity to review what Terraform detected before updating the Terraform state. UPGRADE NOTES: - This release adds some new reserved reference prefixes to make them available for later work. These are `resource.`, `template.`, `arg.`, and `lazy.`. We don't expect these additions to cause problems for most existing configurations, but could cause a conflict if you are using a custom provider which has a resource type named exactly "resource", "template", "arg", or "lazy". In that unlikely event, you can escape references to resources of those types by adding a `resource.` prefix; for example, if you have a `resource "template" "foo"` then you can change references to it from `template.foo` to `resource.template.foo` in order to escape the new meaning. ENHANCEMENTS: - config: The various functions that compute hashs of files on disk, like `filesha256`, will now stream the contents of the given file into the hash function in smaller chunks. Previously they would always read the entire file into memory before hashing it, due to following a similar implementation strategy as the `file` function. ([#28681](https://togithub.com/hashicorp/terraform/issues/28681)) - config: Some new escaping syntax which is not yet useful but will be part of the backward-compatibility story for certain future language editions. ([#28709](https://togithub.com/hashicorp/terraform/issues/28709)) - core: Rsource diagnostics are no longer lost on remote state storage fails ([#28724](https://togithub.com/hashicorp/terraform/issues/28724)) - core: Diagnostics from provisioner failures are now shown in CLI output ([#28753](https://togithub.com/hashicorp/terraform/issues/28753)) - `terraform init`: add a new `-migrate-state` flag instead of automatic state migration, to prevent failing when old backend config is not usable ([#28718](https://togithub.com/hashicorp/terraform/issues/28718)) - `terraform plan` and `terraform apply`: will now report any changes Terraform detects during the "refresh" phase for each managed object, providing confirmation that Terraform has seen those changes and, where appropriate, extra context to help understand the planned change actions that follow. ([#28634](https://togithub.com/hashicorp/terraform/issues/28634)) - `terraform plan` and `terraform apply`: now have a new option `-refresh-only` to activate the "refresh only" planning mode, which causes Terraform to ignore any changes suggested by the configuration but still detect any changes made outside of Terraform since the latest `terraform apply`. ([#28634](https://togithub.com/hashicorp/terraform/issues/28634)) - backend/gcs: Terraform Core now supports [Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation). The federated JSON credentials must be loaded through the `GOOGLE_APPLICATION_CREDENTIALS` environment variable. This is also available in the Google Provider in versions newer than v3.61. ([#28296](https://togithub.com/hashicorp/terraform/issues/28296)) - backend/remote: supports several new CLI options when running plans and applies with Terraform Cloud: `-refresh=false`, `-replace`, and `-refresh-only`. ([#28746](https://togithub.com/hashicorp/terraform/issues/28746)) BUG FIXES: - core: Fix sensitivity handling with plan values, which could cause the sensitive marks to be lost during apply leading to a perpetual diff ([#28687](https://togithub.com/hashicorp/terraform/issues/28687)) - core: Fix crash when specifying SSH `bastion_port` in a resource `connection` block ([#28665](https://togithub.com/hashicorp/terraform/issues/28665)) - core: Terraform will now upgrade and refresh (unless disabled) deposed objects during planning, in a similar manner as for objects that have been removed from the configuration. "Deposed" is how Terraform represents the situation where a `create_before_destroy` replacement failed to destroy the old object, in which case Terraform needs to track both the new and old objects until the old object is successfully deleted. Refreshing these during planning means that you can, if you w

Configuration

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

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

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

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

[ ] If you want to rebase/retry this PR, click this checkbox.

DelineaXPM / terraform-provider-dsv

chore(deps): update ⬆️ golang module github.com/hashicorp/terraform to v1 #18

Release Notes

Configuration

⚠ Artifact update problem

File name: go.sum

Renovate Ignore Notification