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
Plan: 1 to add, 0 to change, 0 to destroy.
╷
│ Error: Alert grouping parameters configuration attribute "time_window" is only supported by "intelligent" type Alert Grouping
│
│ with module.pagerduty_services.pagerduty_service.services["my_service"],
│ on pagerduty_services/main.tf line 6, in resource "pagerduty_service" "services":
│ 6: resource "pagerduty_service" "services" {
│
Expected Behavior
It should be okay to set a time_window even if the type is content_based.
Indeed manually tweaking the "Alerts may be grouped if they arrive within a XXX window" setting is possible whatever the alert grouping type is chosen.
Actual Behavior
Setting a time_window is not possible if the type is content_based.
Steps to Reproduce
Create a pagerduty_service with the given alert_grouping_parameters
Run terraform apply
Important Factoids
Issue occurs on all versions providing the time_window setting (version >= 3.2.0)
References
Some other recent issue on the content_based type: #778
The text was updated successfully, but these errors were encountered:
Terraform Version
Affected Resource(s)
pagerduty_service
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Debug Output
Expected Behavior
It should be okay to set a
time_window
even if the type iscontent_based
.Indeed manually tweaking the "Alerts may be grouped if they arrive within a XXX window" setting is possible whatever the alert grouping type is chosen.
Actual Behavior
Setting a
time_window
is not possible if the type iscontent_based
.Steps to Reproduce
pagerduty_service
with the givenalert_grouping_parameters
terraform apply
Important Factoids
Issue occurs on all versions providing the
time_window
setting (version >= 3.2.0)References
Some other recent issue on the
content_based
type: #778The text was updated successfully, but these errors were encountered: