From 021137454b6991e06f35a8f5fd35eec4f18c3bcf Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Mon, 1 Nov 2021 08:52:37 -0700 Subject: [PATCH] Update CHANGELOG.md --- CHANGELOG.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1c928a8e5..6d874f591 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,9 @@ UPGRADE NOTES: 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 module users to manually run `terraform state mv` after upgrading to a newer module version, as long as the change is expressible as static configuration. However, `terraform state mv` remains available for use in more complex migration situations that are not well-suited to declarative configuration. * A new `cloud` option in the `terraform` settings block adds a more native integration for Terraform Cloud and its [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/Enterprise users with actionable error messages and prompts. ([#29826](https://github.com/hashicorp/terraform/pull/29826)) * `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://github.com/hashicorp/terraform/pull/29637)) * `terraform plan` and `terraform apply`: When Terraform automatically moves a singleton resource instance to index zero or vice-versa in response to adding or removing `count`, it'll report explicitly that it did so as part of the plan output. ([#29605](https://github.com/hashicorp/terraform/pull/29605))