Question

A team originally deployed three S3 buckets using count, creating addresses like aws_s3_bucket.data[0], [1], and [2]. They refactored the configuration to use for_each with a map keyed by "logs", "backup", and "archive". Running terraform plan now shows Terraform wants to destroy the three indexed buckets and create three new keyed ones. Which action lets them adopt the new addressing without destroying and recreating the buckets?

Accepted Answer

Run terraform state mv for each resource, e.g. terraform state mv 'aws_s3_bucket.data[0]' 'aws_s3_bucket.data["logs"]'

Answer

Run terraform state rm on all three buckets so Terraform stops tracking them, then apply

Answer

Run terraform apply and accept the destroy/create because count and for_each addresses are always interchangeable

Answer

Run terraform refresh to update the state so it matches the new for_each keys automatically