Closed l-alfaro closed 4 months 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-248530 was created for internal tracking.
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!
Hi @l-alfaro thanks for opening this issue with us. Just so I understand correctly: is this error happening when you are trying to delete the alert configuration from the TF script? Was that same alert configuration created through TF as well?
What the error is indicating is that it might be that you used different keys to create these alerts. I haven't tried to replicate locally, I'll wait for more updates before trying
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!
Is there an existing issue for this?
Provider Version
v1.16.0
Terraform Version
v1.6.2 (OpenTofu)
Terraform Edition
Terraform Open Source (OSS)
Current Behavior
We are getting the following error in our plans after removing the alert configuration to address a drift result:
The removal of the resource is the only change being made. Adding it back results in the plan succeeding again.
Terraform configuration to reproduce the issue
Steps To Reproduce
mongodbatlas_alert_configuration
resource block form TF codeLogs
No response
Code of Conduct