Question

Your team is splitting a large Terraform configuration into two separate root modules, each with its own remote backend state file. A resource named aws_db_instance.primary currently exists in the original state file but should now be managed by the new configuration without destroying and recreating the live database. Which approach correctly moves this resource between the two separate state files?

Accepted Answer

Run 'terraform state mv -state-out=new.tfstate aws_db_instance.primary aws_db_instance.primary' after pulling both states locally, then push the updated states to their respective backends

Answer

Run 'terraform state rm aws_db_instance.primary' in the old configuration and 'terraform apply' in the new configuration to recreate it

Answer

Run 'terraform import aws_db_instance.primary <db-id>' in the new configuration only, leaving the old state untouched

Answer

Copy the entire old state file into the new backend and run 'terraform refresh'