Closed SamuelMolling closed 1 year ago
@SamuelMolling Was able to duplicate skipped terragrunt portion will track issue in engineering ticket INTMDB-597
I'm waiting. Thanks!
@SamuelMolling I did a bit more testing and found way to import to make state file apply properly I used IP addresses to match your use of ip_address in example you provided If I include index_id [\"1.2.3.4\"] to import it will build a proper state that works on next apply without [\"1.2.3.4\"] it imports a single value and it trips over next IP Address
terraform import mongodbatlas_access_list_api_key.default[\"1.2.3.4\"] orgid-apikeyid-1.2.3.4 terraform import mongodbatlas_access_list_api_key.default[\"1.2.3.5\"] orgid-apikeyid-1.2.3.5
closing this issue, but feel free to re-open if you need anything else here.
Terraform CLI and Terraform MongoDB Atlas Provider Version
Terraform Configuration File
Steps to Reproduce
Expected Behavior
Basically the import succeeds, but it doesn't import the ips and when I try to run apply, it says that the ip already exists
Actual Behavior
I try to import, the import succeeds, but it doesn't try to change the resource, just create it.
Debug Output
Attached
Additional Context
The apikey import works, but not the access list