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
resource"grafana_contact_point""teams_contact_point_root" {
name="name-32-chars-here"org_id=grafana_organization.org.idteams {
url=var.teams_webhook_url_roottitle="CUSTOMER MONITORING ALERTS"disable_resolve_message=truemessage=<<EOT{{ if gt (len .Alerts.Firing) 0 }} {{ len .Alerts.Firing }} alert/s firing: {{ range .Alerts.Firing }} {{ template "alert" .}} {{ end }}{{ end }}EOT
}
}
Expected Behavior
Contact point is created
Actual Behavior
500 error with no context at all
Steps to Reproduce
No response
Important Factoids
We're were checking different scenarios which could allow to reproduce the error and turned out if you use name longer than 30 symbols via terraform provider, then you have 500, but the same name works via UI.
References
No response
The text was updated successfully, but these errors were encountered:
makarov-roman
changed the title
POST /api/v1/provisioning/contact-points 500 with no context (name to long)
POST /api/v1/provisioning/contact-points 500 with no context (name too long)
Nov 19, 2024
Terraform Version
1.9.8
Terraform Grafana Provider Version
3.13.1
Grafana Version
11.3.0
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Contact point is created
Actual Behavior
500 error with no context at all
Steps to Reproduce
No response
Important Factoids
We're were checking different scenarios which could allow to reproduce the error and turned out if you use name longer than 30 symbols via terraform provider, then you have 500, but the same name works via UI.
References
No response
The text was updated successfully, but these errors were encountered: