run_b6d2ea3b99a8174d

input

{
  "request": "Triage Jira ticket SREIN-1656: Decommission the fx-sig-verify tenant",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/SREIN-1656"
  ],
  "sourceContext": {
    "issue": "SREIN-1656"
  }
}

summary

SREIN-1656 requests decommissioning of the fx-sig-verify tenant (high risk_level, webservices function) across the global-platform-admin and google-workspace-management repos, plus billing/inventory metadata. The ticket is still in Backlog with zero comments, meaning no work has started and no coordination with the named stakeholder has been confirmed in-thread. The description is thorough and self-contained (tenant file, GCP projects, workgroup file, billing/inventory CSVs, onboarding ticket link), but it explicitly requires human coordination and a decision on data retention before any deletion occurs. Recommend triaging this as "ready to start, pending stakeholder confirmation" rather than immediately actionable, and assigning an engineer to drive the teardown checklist.

findings

• Ticket is unassigned/untouched: status is Backlog with 0 comments, so no engineer has picked it up or confirmed the pre-work with the workgroup admin.
• Ticket names a specific required contact (Jon Buckley / jbuckley@mozilla.com) who must be looped in before/during execution as the workgroup admin, and who has already verbally confirmed deletability, but per-project data retention decisions are still open.
• Scope of the decommission is well-defined and spans multiple repos/files, indicating this is a multi-step, multi-repo change rather than a single PR.
• Tenant is flagged risk_level high, which typically warrants extra caution/change-review before deletion (e.g. confirming no lingering prod traffic, backups, or compliance holds), reinforcing the need for the retention conversation before proceeding.
• An onboarding ticket (OPST-295) is referenced for historical context but could not be retrieved due to access policy restrictions in this session; a human triager with access should review it if deeper history is needed.

proposed actions

Triage note: This looks ready to move out of Backlog once two things are confirmed with Jon Buckley (jbuckley@mozilla.com), the workgroup admin:
1. Data-retention outcome for prod/nonprod project artifacts (GCS buckets, BQ datasets, logs) before deletion.
2. Whether the google-workspace-management workgroup fx-sig-verify.yaml should be removed entirely or left in place.

Given risk_level: high on the tenant definition, suggest treating this as a checklist-driven teardown across the listed repos/files:
- mozilla/global-platform-admin: tenants/fx-sig-verify.yaml, projects/tf/webservices/locals.tf (moz-fx-fx-sig-verify-nonprod, moz-fx-fx-sig-verify-prod)
- google-workspace-management: tf/workgroups/fx-sig-verify.yaml
- billingetl: data/app_entity.csv, data/app_product_attribution.csv, inventoryv1/{application_registry,gcp_mapping,aws_mapping}.csv

Recommend: (a) assign an owner and move to In Progress once Jon's retention/workgroup answers are captured here, (b) snapshot/export any BQ datasets or bucket contents flagged for retention prior to project deletion, (c) cross-link OPST-295 for onboarding-time context if useful, (d) after teardown, verify billing/inventory CSVs no longer list the app_code and confirm no orphaned IAM bindings remain referencing the deleted projects.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "SREIN-1656"
    },
    "result": {
      "key": "SREIN-1656",
      "summary": "Decommission the fx-sig-verify tenant",
      "status": "Backlog",
      "description_text": "The  fx-sig-verify  tenant is no longer in use and can be decommissioned. Note:  Talk to Jon Buckley (jbuckley@mozilla.com) before/while executing \u2014 he has already confirmed the tenant can be deleted, but he's the workgroup admin and the right person to coordinate the teardown with. Scope (mozilla/global-platform-admin): Tenant definition:  tenants/fx-sig-verify.yaml  (app_code  fx-sig-verify , function  webservices , risk_level  high ) GCP projects:  moz-fx-fx-sig-verify-nonprod  (dev, stage) and  moz-fx-fx-sig-verify-prod  (prod) Project entry:  projects/tf/webservices/locals.tf Workgroup:  google-workspace-management/tf/workgroups/fx-sig-verify.yaml  (sponsor htahsildoost@mozilla.com, admins jbuck + servicessre/admins) Billing/inventory metadata:  billingetl/data/app_entity.csv ,  billingetl/data/app_product_attribution.csv ,  billingetl/inventoryv1/{application_registry,gcp_mapping,aws_mapping}.csv Original onboarding ticket:  https://mozilla-hub.atlassian.net/browse/OPST-295 Please confirm the desired data-retention outcome for anything in the projects (buckets, BQ datasets, logs) with jbuckley before deletion, and whether the workgroup itself should be removed or left in place.",
      "comment_count": 0,
      "comments": []
    }
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "OPST-295"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "OPST-295"
      }
    },
    "blocked": true
  }
]

log