fix: incidente rule enum recipient to responders

opsgenie · Feb 10, 2023 · f0016fa · f0016fa
1 parent 60930cd
commit f0016fa
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/opsgenie/resource_opsgenie_service_incident_rule.go b/opsgenie/resource_opsgenie_service_incident_rule.go
@@ -58,7 +58,7 @@ func resourceOpsGenieServiceIncidentRule() *schema.Resource {
 										Required: true,
 										ValidateFunc: validation.StringInSlice([]string{
 											"message", "description", "tags",
-											"extra-properties", "recipients", "teams", "priority",
+											"extra-properties", "responders", "teams", "priority",
 											"alias", "source", "entity", "actions", "details",
 										}, false),
 									},

diff --git a/website/docs/r/service_incident_rule.html.markdown b/website/docs/r/service_incident_rule.html.markdown
@@ -69,7 +69,7 @@ The `incident_rule` block supports:
 
 The `conditions` block supports:
 
-* `field` - (Required) Specifies which alert field will be used in condition. Possible values are `message`, `alias`, `description`, `source`, `entity`, `tags`, `actions`, `details`, `extra-properties`, `recipients`, `teams`, `priority`
+* `field` - (Required) Specifies which alert field will be used in condition. Possible values are `message`, `alias`, `description`, `source`, `entity`, `tags`, `actions`, `details`, `extra-properties`, `responders`, `teams`, `priority`
 
 * `operation` - (Required) It is the operation that will be executed for the given field and key. Possible operations are `matches`, `contains`, `starts-with`, `ends-with`, `equals`, `contains-key`, `contains-value`, `greater-than`, `less-than`, `is-empty`, `equals-ignore-whitespace`.