Rulesets allow you to route events to an endpoint and create collections of event rules, which define sets of actions to take based on event content.
Rulesets and Event Rules will end-of-life soon. We highly recommend that you migrate to Event Orchestration as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, REST APIs and Terraform support, advanced conditions, and rule nesting.
resource "pagerduty_team" "foo" {
name = "Engineering (Seattle)"
}
resource "pagerduty_ruleset" "foo" {
name = "Primary Ruleset"
team {
id = pagerduty_team.foo.id
}
}
The following arguments are supported:
name
- (Required) Name of the ruleset.team
- (Optional) Reference to the team that owns the ruleset. If none is specified, only admins have access.The following attributes are exported:
id
- The ID of the ruleset.routing_keys
- Routing keys routed to this ruleset.type
- Type of ruleset. Currently, only sets to global
.Rulesets can be imported using the id
, e.g.
$ terraform import pagerduty_ruleset.main 19acac92-027a-4ea0-b06c-bbf516519601