Open mrinella-fs opened 4 years ago
Hey @mrinella-fs π Thank you for taking the time to file this issue. Given that there's been a number of Terraform and AWS provider releases since you initially filed it, can you confirm if you're still experiencing this behavior?
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!
I am attempting to import a few existing aws resources into an existing state that are in a different region than the default provider in this terraform workspace. The backend is terraform cloud, so the action is happening there.
For both of the attempts I have made, the result is:
Error: Cannot import non-existent remote object
The commands I am running:
terraform import -provider=aws.prod-us-east-2 aws_vpc. vpc-
terraform import -provider=aws.prod-us-east-2 aws_vpc_dhcp_options. dopt-
terraform version 0.12.23 aws provider version 2.54
I can assure you the places where I obscured the names and the ids were checked many times and I do have them correct. The provider name is also correct for this codebase. The default provider region is us-east-1. I have built things in both regions in this codebase. I'm just trying to bring in some existing items now.
Hopefully I'm doing something wrong and its easy.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
0000