{
"request": "Triage Jira ticket MZCLD-3671: Adopt the 94 PagerDuty services that are not managed in Terraform",
"references": [
"https://mozilla-hub.atlassian.net/browse/MZCLD-3671"
],
"sourceContext": {
"issue": "MZCLD-3671"
}
}MZCLD-3671 is a well-scoped backlog item to bring PagitagerDuty configuration under IaC. It proposes adopting the 94 unmanaged PagerDuty services (129 keyed integrations) into Terraform (global-platform-admin/pagerduty), staged in batches to avoid clobbering services mid-migration off the legacy moz-svc-ops.pagerduty.com account. The ticket is currently unactioned (Backlog, 0 comments) and is explicitly blocked/gated by two dependencies (MZCLD-3670 and the moz-svc-ops consolidation effort) that could not be independently verified here (access to MZCLD-3670 and OPST-2460 was blocked by policy in this run). Triage recommendation: confirm dependency status before scheduling work, and set up the staged adoption plan with re-measurement checkpoints as the ticket's acceptance criteria already specify.
[
{
"capability": "jira.issue.read",
"args": {
"key": "MZCLD-3671"
},
"result": {
"key": "MZCLD-3671",
"summary": "Adopt the 94 PagerDuty services that are not managed in Terraform",
"status": "Backlog",
"description_text": "Context: Surfaced while closing OPST-2460 (PagerDuty API key rotation). Depends on MZCLD-3670; gated on the moz-svc-ops consolidation. Problem. Measured 2026-08-05 via the PagerDuty API, mozilla.pagerduty.com has 131 services with 182 keyed integrations : Services Keyed integrations Managed in Terraform 37 53 Not in Terraform 94 129 So ~71% of the paging surface sits entirely outside IaC . For that majority there is no rotation path, no audit trail and no recorded ownership \u2014 you cannot rotate what you do not manage. This is the root cause behind the original OPST-2460 question. Caveat: some of the 94 are likely duplicates or in-flight migrations from the legacy moz-svc-ops.pagerduty.com account, which the Foundational SRE Program has been consolidating off since June 2025. This must therefore be staged, not bulk-imported. Ask. Adopt the unmanaged services into global-platform-admin/pagerduty in batches, skipping anything the consolidation is about to retire. Acceptance criteria. Every live service in mozilla.pagerduty.com is either managed in Terraform or explicitly recorded as pending decommission. No service is adopted that is scheduled for retirement. The Terraform-vs-live coverage figure is re-measured after each batch.",
"comment_count": 0,
"comments": []
}
},
{
"capability": "jira.issue.read",
"args": {
"key": "MZCLD-3670"
},
"result": {
"error": "read blocked by policy: resource not in run subject",
"args": {
"key": "MZCLD-3670"
}
},
"blocked": true
},
{
"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
}
]{
"model": "claude-sonnet-5",
"input_tokens": 5873,
"output_tokens": 2264,
"estimated_cost_usd": 0.051579
}[]