Closed nick-augustine closed 16 hours ago
Thanks for opening this issue! Please make sure you've followed our guidelines when opening the issue. In short, to help us reproduce the issue we need:
The ticket CLOUDP-253876 was created for internal tracking.
@nick-augustine Thank you for creating this issue! I was able to reproduce this issue. We are working on the fix for this issue which should be available in our next release.
This issue has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!
bump
This issue has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!
Looks like this has been fixed in #2349 and released in 1.17.2
.
Is there an existing issue for this?
Provider Version
1.17.0
Terraform Version
1.8.3
Terraform Edition
Terraform Cloud
Current Behavior
When a resource
mongodbatlas_project_ip_access_list
is removed from the list of networks in the Mongo Cloud UI, we're expecting Terraform to be used to create that again or remove and create new entries duringterraform applies
. The current behavior of this resource will generate an error when attempting to read the state during aterraform plan
-If the resource is removed from terraform state, the plan will successfully run.
terraform state rm 'module.dev_project.mongodbatlas_project_ip_access_list.default["170.85.0.0/16"]'
Terraform configuration to reproduce the issue
Steps To Reproduce
mongodbatlas_project_ip_access_list
with Terraform codeterraform plan
to recreate the resource.Logs
No response
Code of Conduct