Thomas Hervé
Thomas Hervé
Feel free to reopen with more information.
Ah this is in the response, so I think it's read-only? I'll reach out to the monitor team.
Hi, We don't have such a plan right now. The problem I believe is that it requires both a new widget resource and a new dashboard resource, or at least...
My idea would be using the `local_file` provider as widget content, but I haven't tried it.
Hi, What's the provider version you're using? Thanks.
The recommended approach is to add the `force_delete` flag on the resources. This way we skip the server side validation happening when deleting resources.
Hi, The main thing with the JSON resource is that error reporting and validation is more lax, as most of the work happens at apply as there is no schema....
The dashboard team is continuously adding new widgets so while we're catching up, there is an inherent delay between features in the UI and in terraform. If you have specific...
Are you sure you're not seeing another issue? I'm using 3.15.1 and the following examples worked fine: ```hcl resource "datadog_monitor" "rum_new_error_monitors" { for_each = toset(["app1","app2"]) name = "${each.value} | error...