terraform-provider-upgrade

Terraform moved blocks are used during provider upgrades to safely map deprecated resources to their new equivalents without destroying and recreating infrastructure. The upgrade process automatically suggests these moved blocks to ensure your state file tracks resources correctly across major version changes.

Updating Terraform provider version constraints involves modifying the versions.tf file to target the new major release and ensuring provider blocks align with updated APIs. Automation tools retrieve the target upgrade guide, apply necessary migrations, and validate these changes through your CI pipeline.

Breaking changes during Terraform AzureRM migrations often include removed or renamed resources that fail without proper state management. The upgrade process detects these changes, maps deprecated resources to new ones, and generates a TERRAFORM_UPGRADE_BREAKING_CHANGES.md document detailing required configuration updates.

Terraform state management during provider upgrades relies on moved blocks to remap resources to their new types automatically. This prevents state drift and resource recreation, ensuring that the existing infrastructure remains intact while the state file transitions to the new provider schema.

You do not need to manually edit provider blocks when using automated upgrade tools. The process updates versions.tf and ensures provider configuration blocks align with the new APIs automatically, reducing the risk of manual configuration errors during major version migrations.