Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Allow self-referencing in datadog_monitor #18226

Closed
hryamzik opened this issue Jun 11, 2018 · 2 comments
Closed

Feature Request: Allow self-referencing in datadog_monitor #18226

hryamzik opened this issue Jun 11, 2018 · 2 comments

Comments

@hryamzik
Copy link

hryamzik commented Jun 11, 2018

Terraform Version

Terraform v0.11.5
+ provider.datadog v1.0.3

Terraform Configuration Files

resource "datadog_monitor" "disk" {
  name                = "Disk"
  type                = "metric alert"
  query               = "avg(last_5m):avg:system.disk.in_use{device:/dev/ad1s1} > ${datadog_monitor.disk.thresholds.critical}"
  message             = "test"

  thresholds {
    warning           = 0.1
    critical          = 0.7
  }
}

Debug Output

Error: datadog_monitor.disk: datadog_monitor.disk: self reference not allowed: "datadog_monitor.disk.thresholds.critical"

Expected Behavior

Working without errors... The problem here is that critical must mach value in a queue so currently it has to be updated in two places for the same resource.

Steps to Reproduce

  1. terraform init
  2. terraform apply

References

@ghost
Copy link

ghost commented Jun 11, 2018

This issue has been automatically migrated to terraform-providers/terraform-provider-datadog#74 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to terraform-providers/terraform-provider-datadog#74.

@ghost ghost closed this as completed Jun 11, 2018
@ghost
Copy link

ghost commented Apr 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 3, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants