run_69d87a78837a8d29

input

{
  "request": "Triage Jira ticket MZCLD-3670: Extend pagerduty/modules/service to cover the legacy PagerDuty integration types",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3670"
  ],
  "sourceContext": {
    "issue": "MZCLD-3670"
  }
}

summary

MZCLD-3670 is a well-formed backlog engineering task asking for a decision + implementation work on the `pagerduty/modules/service` Terraform module. It was surfaced during OPST-2460 (PagerDuty API key rotation) as a blocker for importing 129 unmanaged PagerDuty integrations into Terraform. The module currently only supports 8 integration types (events_api_v2, pingdom, email, grafana, cloudwatch, newrelic, stackdriver, nagios), but the 129 orphaned integrations are dominated by five legacy/deprecated integration types not modeled by the module. The ticket has no comments yet and is unassigned/untriaged (status: Backlog). No linked runbook or Confluence design doc was referenced in the description to pull additional context from.

findings

• Ticket clearly defines the problem, a measured data snapshot, and acceptance criteria, making it actionable as-is — the main gap is a decision on approach (extend module vs. migrate integrations) rather than missing requirements.
• The 129 unmanaged integrations are overwhelmingly legacy/inbound integration types, with only 27 (~21%) already on the modern events_api_v2 type — meaning a 'migrate to events_api_v2' decision would require touching the majority of integrations, not just a module change.
• This ticket is an explicit prerequisite for a follow-on effort (adopting/importing the unmanaged PagerDuty services into Terraform), so its priority should likely be aligned with that dependent work.
• No Confluence runbook/design doc is linked in the ticket, and OPST-2460 could not be retrieved (access blocked by policy), so full upstream context on the API key rotation project could not be independently verified.
• Ticket currently has zero comments and sits in Backlog status, suggesting it has not yet been triaged/assigned or discussed by the team despite containing concrete, actionable data.

proposed actions

Triage notes: This is a solid, actionable ticket with clear acceptance criteria and good supporting data (integration-type counts as of 2026-08-05). Recommend moving out of Backlog and making an explicit per-type decision before scoping implementation work:

- Given only 27/129 (~21%) unmanaged integrations are already events_api_v2, a blanket 'migrate everything to events_api_v2' approach implies touching ~102 integrations across teams — worth checking whether events_api_v2 is a functional drop-in for the inbound/nagios/app-event-transform types (payload formats/transform logic differ) before committing to that path.
- Suggest a lightweight decision matrix per type: (1) event_transformer_api_inbound_integration (44) and app_event_transform_inbound_integration (27) likely need custom transform logic — evaluate module support vs. migration cost per consuming service, not as one global decision. (2) nagios_inbound_integration (21) may already be coverable by extending the existing `nagios` type in the module rather than migrating. (3) generic_events_api_inbound_integration (9) and change_event_transform_inbound_integration (1) are low-volume — likely cheaper to migrate to events_api_v2 than to add module support for a handful of integrations.
- Since this blocks adoption of the unmanaged PagerDuty services (and traces back to OPST-2460), recommend prioritizing/linking it to that follow-on Terraform-import epic and assigning an owner so the per-type decision can be recorded and reviewed.
- Consider linking this ticket to OPST-2460 explicitly (via 'relates to'/'blocks') if not already linked, for traceability.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3670"
    },
    "result": {
      "key": "MZCLD-3670",
      "summary": "Extend pagerduty/modules/service to cover the legacy PagerDuty integration types",
      "status": "Backlog",
      "description_text": "Context:  Surfaced while closing OPST-2460 (PagerDuty API key rotation). Prerequisite for adopting the unmanaged PagerDuty services. Problem.   global-platform-admin/pagerduty/tf/modules/service  only models these integrations:  events_api_v2 ,  pingdom ,  email ,  grafana ,  cloudwatch ,  newrelic ,  stackdriver ,  nagios . The 129 keyed integrations that are  not  in Terraform are dominated by types the module cannot express (measured 2026-08-05 via the PagerDuty API): Count Type 44 event_transformer_api_inbound_integration 27 app_event_transform_inbound_integration 27 events_api_v2_inbound_integration 21 nagios_inbound_integration 9 generic_events_api_inbound_integration 1 change_event_transform_inbound_integration Only 27 of the 129 are the modern  events_api_v2  type. So adopting those services into Terraform is not a plain  import  \u2014 the module has to grow first, or the integrations have to be migrated. Ask.  Either add support for the missing integration types to the module, or decide that they should be migrated to  events_api_v2  and document that migration path. Acceptance criteria. Every integration type present in  mozilla.pagerduty.com  can either be expressed by  modules/service  or has a documented migration target. The decision (support vs. migrate) is recorded per type.",
      "comment_count": 0,
      "comments": []
    }
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "OPST-2460"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "OPST-2460"
      }
    },
    "blocked": true
  }
]

log