agentplat▸control runs deployments agents metering + agent
← runs

run_4892cf46c0274d40

AWAITING_APPROVAL retrigger →
jira-triage v1 · jira-triage-k8s · owner ingest:jira-new-ticket (api) · via jira-new-ticket · cloud-engineering

input

{
  "request": "Triage Jira ticket MZCLD-3781: GitHub App organization install and repository selections managed in IaC",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3781"
  ],
  "sourceContext": {
    "issue": "MZCLD-3781"
  }
}

summary

MZCLD-3781 is a Backlog, uncommented feature request to move GitHub App organization installation and repository-selection settings from manual ("clickops," GHE-admin-only) configuration into Infrastructure as Code. The ticket itself poses an open question — which GitHub orgs (mozilla is named, others unspecified) need this — and has no linked runbook/design doc to consult. Triage should focus on scoping that question and identifying an IaC mechanism/owner before this can move out of Backlog.

findings

  • Ticket is in Backlog status with zero comments, so no prior discussion or decisions exist to build on.
  • The core problem: GitHub App org install + repo selection is currently changed manually via the GitHub Enterprise UI, requiring GHE admin privileges — a bottleneck and single point of failure/knowledge silo.
  • The ticket explicitly leaves scope undefined: it names 'mozilla' as one org to roll out to but asks 'what else?' — this is an open question blocking implementation, not just a technical unknown.
  • No Confluence runbook or design doc is referenced in the ticket, so there is no existing IaC pattern documented for this specific GitHub App configuration; likely needs a design/spike before implementation, and should check for existing Terraform/GitHub provider usage elsewhere in the org's IaC repos.

proposed actions

jira.comment.postrisk low
MZCLD-3781
Triage note: This looks like a solid candidate for the GitHub Terraform provider (e.g. `github_app_installation_repositories` / org-level app install resources) to replace the current clickops flow, but before moving out of Backlog we need to close the open scoping question in the description: which GitHub orgs beyond `mozilla-services`/`mozilla` (e.g. mozilla-services, mozilla-mobile, mozilla-extensions, etc.) actually have this GitHub App installed today? Suggest: (1) someone with current GHE admin access enumerates all orgs where the App is installed and which repos are selected, (2) confirm whether we already manage any GitHub org/repo config in existing IaC (Terraform) that this could extend, and (3) size the work as a small spike to produce the org list + a design comment before estimating implementation. Flagging for refinement/backlog grooming with an owner assigned to gather the org list.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3781"
    },
    "result": {
      "key": "MZCLD-3781",
      "summary": "GitHub App organization install and repository selections managed in IaC",
      "status": "Backlog",
      "description_text": "Currently these settings are clickops, and you need GHE admin access to change them. Putting them in IaC means they\u2019ll be manageable by more people. What orgs does this need to be rolled out for?  mozilla , what else?",
      "comment_count": 0,
      "comments": []
    }
  }
]

usage

{
  "model": "claude-sonnet-5",
  "input_tokens": 3090,
  "output_tokens": 1195,
  "estimated_cost_usd": 0.027195
}

approvals

[]

log

launched k8s job run-run-4892cf46c0274d40 in ns/mzcld-demo-dev image=us-docker.pkg.dev/moz-fx-mzcld-demo-prod/mzcld-demo-prod/agentplat:latest
runner started
live reasoning model=claude-sonnet-5
awaiting approval for 1 action(s)