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

PagerDuty setting for grafana_alert_notification is coerced into an invalid value #35

Closed
philipcristiano opened this issue Oct 9, 2018 · 4 comments

Comments

@philipcristiano
Copy link

philipcristiano commented Oct 9, 2018

While trying to set grafana_alert_notifications I ran into a problem with the setting for PagerDuty type setting of autoResolve being set to a value that didn't work for Grafana.

Terraform Version

0.11.7

Affected Resource(s)

  • grafana_alert_notification

Terraform Configuration Files

resource "grafana_alert_notification" "pagerduty" {
  name = "${var.service_name} - PagerDuty"
  type = "pagerduty"
  is_default = false

  settings {
    "integrationKey" = "${pagerduty_service_integration.grafana.integration_key}"
    "autoResolve" = true
  }
}

Debug Output

Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

Expected Behavior

The alert notification should have an enabled autoResolve.

Actual Behavior

The value in Grafana appears to be a "1" even when the HCL has true. This results in a defaulted false for the behavior. The "1" is stored in the Grafana DB (as relayed to me by a Grafana.com staff member.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform apply

Important Factoids

Using hosted grafana.com

References

I'll add more debug information as I can gain access to it.

@philipcristiano
Copy link
Author

Thanks! Any info about when this might get a release?

@mlclmj
Copy link
Contributor

mlclmj commented Nov 15, 2018

@philipcristiano Sorry for the delay with this, I'm working on a release at the moment. Will update you here when it's done!

@philipcristiano
Copy link
Author

Wonderful!

@mlclmj
Copy link
Contributor

mlclmj commented Nov 16, 2018

1.3.0 Should be available now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants