[Bnjis]

What

Adds support for the reroute_to_team action in datadog_on_call_team_routing_rules. This action reroutes a matching page to another team's routing rules.

rule {
  query = "tags.service:checkout"
  action {
    reroute_to_team {
      destination_team_id = datadog_team.checkout.id
    }
  }
}

Why

The On-Call routing rules API now accepts a reroute_to_team action ({"type": "reroute_to_team", "destination_team_id": "<team uuid>"}), but it couldn't be managed from Terraform.

Changes

• Bump datadog-api-client-go to a commit that includes RoutingRuleRerouteToTeamAction.
• New action.reroute_to_team block with a destination_team_id attribute, validated as a UUID at plan time. The API returns the action on read, so plan, apply and import round-trip it.
• Validate() applies the API's constraints at apply time, before the request is sent, so they fail early with a clear error:
  • destination_team_id is required.
  • At most one reroute_to_team action per rule.
  • A reroute can only be combined with send_slack_message or send_teams_message. Combining it with escalation_policy (attribute or action) or trigger_workflow_automation is rejected.
• Update the example and the hand-maintained docs page.

Testing

• New TestAccOnCallTeamRoutingRulesRerouteToTeam: creates three teams and reroutes two rules to them, swaps the destinations (update), then runs an ImportStateVerify step. A cassette was recorded.
• New TestAccOnCallTeamRoutingRulesRerouteToTeamValidation: covers the validation errors. The cassette has no interactions.
• TestAccOnCallTeamRoutingRules* pass in replay mode, including the existing tests with the bumped client.
• make test, make fmtcheck, make vet and make check-docs pass.

[Bnjis]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-13 08:20:17 UTC ℹ️ Start processing command /merge

---

2026-10-13 08:20:19 UTC ❌ MergeQueue

PR already in the queue with status in_progress