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"pagerduty_service""integration_test2" {
name="[TESTING] Integration Test Service 2"escalation_policy=...alert_creation="create_alerts_and_incidents"incident_urgency_rule {
type="constant"urgency="low"
}
}
resource"pagerduty_alert_grouping_setting""integration_test2" {
name="Default Alert Grouping for all engineering systems"type="content_based_intelligent"services=[pagerduty_service.integration_test2.id]
config {
aggregate="all"fields=["severity"]
time_window=300
}
}
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
change anything on the pagerduty_service e.g. name = "[TESTING] Integration Test Service 2a"
terraform apply again
Expected Behavior
pagerduty_service should change accordingly e.g. name should now be "[TESTING] Integration Test Service 2a"
Actual Behavior
Error: Error reading: P36WBBS: PUT API call to https://api.pagerduty.com/services/P36WBBS failed 400 Bad Request. Code: 2001, Errors: [Alert grouping is invalid.], Message: Invalid Input Provided
with pagerduty_service.integration_test2,
on main.tf line 43, in resource "pagerduty_service" "integration_test2":
43: resource "pagerduty_service" "integration_test2" {
}
The error specifically happens when using the new content_based_intelligent setting in pagerduty_alert_grouping_setting, I suspect because it's not a valid alert grouping for the pagerduty_service resource.
Workaround
Don't use the new content_based_intelligent setting.
The text was updated successfully, but these errors were encountered:
Terraform Version
Terraform v1.9.7
Affected Resource(s)
Terraform Configuration Files
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
pagerduty_service
e.g.name = "[TESTING] Integration Test Service 2a"
terraform apply
againExpected Behavior
pagerduty_service
should change accordingly e.g. name should now be "[TESTING] Integration Test Service 2a"Actual Behavior
The error specifically happens when using the new
content_based_intelligent
setting inpagerduty_alert_grouping_setting
, I suspect because it's not a valid alert grouping for thepagerduty_service
resource.Workaround
Don't use the new
content_based_intelligent
setting.The text was updated successfully, but these errors were encountered: