run_c89da9827c1bad05

input

{
  "request": "Triage Jira ticket MZCLD-3806: Invalidate cache for cloud objects for FxA",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3806"
  ],
  "sourceContext": {
    "issue": "MZCLD-3806"
  }
}

summary

MZCLD-3806 requests invalidation of GCP CDN cache for two FxA static asset manifest paths in both stage and prod environments. The ticket is well-specified with exact gcloud commands, but is still sitting in Backlog with no comments, owner, or execution confirmation. Triage recommendation: confirm whether this is a one-time fix or recurring need, verify current status of the referenced asset manifest issue, and get the commands run (or scheduled) by someone with access to the moz-fx-fxa-prod and moz-fx-fxa-nonprod GCP projects.

findings

• Ticket provides exact, ready-to-run gcloud commands for both prod and stage CDN cache invalidation targeting the static-asset-manifest.json path.
• Ticket description references a related issue ('This is related to this issue') but the link/reference appears to have been stripped or lost in the description text, so root cause/urgency context is missing.
• Ticket has zero comments and is still in Backlog status, indicating no triage or execution has occurred yet.
• No linked Confluence runbook or design doc was found in the ticket to reference for additional operational context.

proposed actions

Thanks for filing this. A few triage notes before we execute:

1) The description references "this issue" as related context, but the link appears to have been dropped when the ticket was created — could you add the linked issue/PR so we have the root cause (e.g., a stale asset manifest causing 404s/broken deploys)?
2) The commands look correct and low-risk (CDN cache invalidation only, no data changes):
   - Prod: `gcloud compute url-maps invalidate-cdn-cache fxa-prod-content-cdn --path "/settings/prod/static/static-asset-manifest.json" --project moz-fx-fxa-prod`
   - Stage: `gcloud compute url-maps invalidate-cdn-cache fxa-stage-content-cdn --path "/settings/stage/static/static-asset-manifest.json" --project moz-fx-fxa-nonprod`
3) Please confirm: is this a one-time invalidation to unblock a current issue, or should it be run on every deploy (in which case it may belong in the deploy pipeline rather than as a manual ticket)?
4) Once confirmed, whoever has IAM access to moz-fx-fxa-prod and moz-fx-fxa-nonprod can run both commands — recommend stage first, verify, then prod. Moving to 'Ready for work' pending the linked-issue clarification.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3806"
    },
    "result": {
      "key": "MZCLD-3806",
      "summary": "Invalidate cache for cloud objects for FxA",
      "status": "Backlog",
      "description_text": "This needs to happen for stage and prod.   Prod: gcloud compute url-maps invalidate-cdn-cache fxa-prod-content-cdn \\\n  --path \"/settings/prod/static/static-asset-manifest.json\" \\\n  --project moz-fx-fxa-prod Stage: gcloud compute url-maps invalidate-cdn-cache fxa-stage-content-cdn \\\n  --path \"/settings/stage/static/static-asset-manifest.json\" \\\n  --project moz-fx-fxa-nonprod This is related to this issue",
      "comment_count": 0,
      "comments": []
    }
  }
]

log