run_1750c1f28c312a85

input

{
  "request": "Triage Jira ticket MZCLD-3830: Cloud Run functionality for web apps",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3830"
  ],
  "sourceContext": {
    "issue": "MZCLD-3830"
  }
}

summary

findings

• none

proposed actions

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3830"
    },
    "result": {
      "key": "MZCLD-3830",
      "summary": "Cloud Run functionality for web apps",
      "status": "Backlog",
      "description_text": "Background There is no supported MozCloud path today for a web app that needs a running server but does not warrant a Kubernetes deployment. The options are Quick ( https://quick.mozilla.cloud/ ), which handles static sites only (MZCLD-3253 / MZCLD-3254), or full MozCloud onboarding onto GKE. Cloud Run sits between them. Cloud Run is already in production use inside MozCloud, but only as one-off implementations \u2014 never as a documented paved path: MZCLD-3551 \u2014 FinOps dashboards at  finops.mozilla.cloud : Cloud Run behind an HTTPS load balancer with IAP and a custom OAuth client, modeled on  webservices-infra quick/tf . This is the reusable pattern. MZCLD-2575 \u2014 PagerDuty to Google Doc webhook service. MZCLD-3162 \u2014 AMO addons-customs-scanner, a Cloud Run function that cannot be deployed via ArgoCD. MZCLD-791 \u2014 Slack PAM-integration Cloud Run service. The gap was first named under Heroku sunset: MZCLD-2181 proposed recommending Cloud Run to teams, and MZCLD-2183 was opened to write that guidance. It has sat in Backlog, unassigned, with an empty description. Goal Generalize the pattern MZCLD-3551 proved out into a repeatable Cloud Run path for web apps \u2014 reusable Terraform, Mozilla SSO / IAP by default, a  mozilla.cloud  vanity domain story, and clear decision guidance on when Cloud Run is the right answer versus Quick or GKE. Note Data Eng is also working on this for BQ or other data related web apps. Coordinate before building so MozCloud and Data Engineering do not produce two divergent Cloud Run patterns. Out of scope Cloud Run  Jobs  for batch/ETL work. That is covered under MZCLD-3538 (Billing ETL Platform and Airflow Migration), which is deliberately moving  off  Cloud Run onto Airflow.",
      "comment_count": 0,
      "comments": []
    }
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3551"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "MZCLD-3551"
      }
    },
    "blocked": true
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-2183"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "MZCLD-2183"
      }
    },
    "blocked": true
  }
]

log