You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`mongodbatlas_alert_configuration` resource attribute `notification.#.integration_id` may have a computed value due to recent updates in the Atlas API [Alert Configuration](https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/getAlertConfiguration). Due to this, MongoDB Atlas Provider versions **1.16.0 to 1.19.0** may experience non-empty plans if you are using this resource with an integration set for the notifications without an explicitly set `integration_id`. For more details, see [#2603](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/2603).
24
+
25
+
These users should either:
26
+
27
+
- Upgrade to the latest MongoDB Atlas Terraform Provider (1.20.0) to avoid the non-empty plan, or
28
+
- Update Terraform configurations to include the `integration_id` returned in the non-empty plan as:
29
+
```
30
+
notification {
31
+
type_name = "DATADOG"
32
+
integration_id = "xxxxxxxxxxxxxxxxxxxxxxxx" # add integration_id shown in the plan to your configuration
Note: Applying the non-empty plan will be a no-op but users will still get the non-empty plan even after applying unless one of the above solutions are adopted.
40
+
41
+
22
42
## New Terraform MongoDB Atlas modules
23
43
You can now leverage our [Terraform Modules](https://registry.terraform.io/namespaces/terraform-mongodbatlas-modules) to easily get started with MongoDB Atlas and critical features like [Push-based log export](https://registry.terraform.io/modules/terraform-mongodbatlas-modules/push-based-log-export/mongodbatlas/latest), [Private Endpoints](https://registry.terraform.io/modules/terraform-mongodbatlas-modules/private-endpoint/mongodbatlas/latest), etc.
0 commit comments