Name update of aws_vpn_connection_route resource caused unwanted effects

[hashibot]

This issue was originally opened by @jwadolowski as hashicorp/terraform#4341. It was migrated here as part of the provider split. The original body of the issue is below.

---

Hey,

I've just renamed 2 aws_vpn_connection_route resources (all arguments stayed the same) and applied the changes, but it turned out my static routes ended in deleted state.

This is how plan looked like:

+ aws_vpn_connection_route.cognifide-office-int-route
    destination_cidr_block: "" => "192.168.0.0/16"
    vpn_connection_id:      "" => "vpn-48bdca03"

- aws_vpn_connection_route.cognifide-office-route

+ aws_vpn_connection_route.cognifide-vpn-int-route
    destination_cidr_block: "" => "10.214.0.0/16"
    vpn_connection_id:      "" => "vpn-48bdca03"

- aws_vpn_connection_route.cognifide-vpn-route

and this was the output of terraform apply command:

aws_vpn_connection_route.cognifide-office-route: Destroying...
aws_vpn_connection_route.cognifide-vpn-route: Destroying...
aws_vpn_connection_route.cognifide-office-int-route: Creating...
  destination_cidr_block: "" => "192.168.0.0/16"
  vpn_connection_id:      "" => "vpn-48bdca03"
aws_vpn_connection_route.cognifide-vpn-int-route: Creating...
  destination_cidr_block: "" => "10.214.0.0/16"
  vpn_connection_id:      "" => "vpn-48bdca03"
aws_vpn_connection_route.cognifide-office-route: Destruction complete
aws_vpn_connection_route.cognifide-vpn-route: Destruction complete
aws_vpn_connection_route.cognifide-vpn-int-route: Creation complete
aws_vpn_connection_route.cognifide-office-int-route: Creation complete

Apply complete! Resources: 2 added, 0 changed, 2 destroyed.

The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.

State path: .terraform/terraform.tfstate

Immediately after this change I lost connectivity to my EC2 machines. Once I logged in to AWS control panel I saw both routes were in deleted state. After manual change connectivity was restored.

This is the place I've seen these deleted states (unfortunately didn't take screenshot of that):

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!