run_18ebfe9e22bdb65c

input

{
  "request": "Triage Jira ticket MZCLD-3649: Support embedding files into ConfigMaps (.Files.Get) in MozCloud Helm charts",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3649"
  ],
  "sourceContext": {
    "issue": "MZCLD-3649"
  }
}

summary

MZCLD-3649 requests a feature enhancement to MozCloud Helm charts: allow ConfigMap data to be populated from files shipped with the chart/tenant (similar to Helm's built-in `.Files.Get`) rather than requiring file contents to be inlined into values.yaml. This was surfaced as a blocker/pain-point during the llm-proxy migration (MZCLD-2331), where the `litellm-config` ConfigMap needs to embed a `custom_callbacks.py` file. Ticket is currently in Backlog with no comments and no linked runbook/design doc found. This is a legitimate, well-scoped feature request with clear context and acceptance criteria; it needs product/engineering prioritization rather than immediate action.

findings

• Ticket is a feature request, not a bug or incident — current MozCloud ConfigMap chart support only allows inline key/value data.
• Concrete use case driving the request: llm-proxy migration (MZCLD-2331) needs to embed custom_callbacks.py into the litellm-config ConfigMap via Helm's .Files.Get, which today would require pasting the whole file into values.yaml.
• Clear acceptance criteria already defined by the reporter: a ConfigMap key can be populated from a file shipped with the chart/tenant without pasting the file body into values.yaml.
• Ticket has zero comments and is sitting in Backlog status, suggesting it has not yet been triaged/prioritized by the team.
• No linked Confluence runbook or design doc was found in the ticket description; the only related context is Jira issue MZCLD-2331, which was inaccessible to this triage tool (read blocked by policy), so full migration context could not be independently verified.

proposed actions

Thanks for filing this — the use case is clear (llm-proxy's litellm-config ConfigMap needs to embed custom_callbacks.py via `.Files.Get`, and inlining the whole file into values.yaml is brittle). Proposing to move this out of Backlog for scoping. Suggested approach to evaluate: extend the mozcloud ConfigMap chart template to accept a list of file paths/globs (e.g. a `filesFromChart` or `configMap.filesGlob` values key) that get rendered via Helm's `.Files.Get`/`.Files.Glob`, alongside the existing inline `data` map. We should also confirm: (1) whether tenant-supplied files (not just chart-bundled files) need to be supported, since Helm's `.Files.Get` only reads files packaged within the chart itself, and (2) size limits (ConfigMaps are capped at ~1MiB) to ensure custom_callbacks.py and similar files fit. Once scoped, this would unblock the llm-proxy migration (MZCLD-2331) and any other tenants with similar file-embedding needs. Requesting prioritization/sizing from the MozCloud Helm chart maintainers.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3649"
    },
    "result": {
      "key": "MZCLD-3649",
      "summary": "Support embedding files into ConfigMaps (.Files.Get) in MozCloud Helm charts",
      "status": "Backlog",
      "description_text": "Context:  Surfaced during the  llm-proxy  mozcloud migration (MZCLD-2331). Problem.  The mozcloud ConfigMap only supports inline key/value  data . The  llm-proxy   litellm-config  ConfigMap embeds  custom_callbacks.py  via Helm's  .Files.Get . Migrating today would require inlining the entire file contents into the values file, which is brittle and hard to maintain. Ask.  Provide a way to include file contents from the chart (e.g.  .Files.Get  / a file-glob input) into a ConfigMap without manually inlining them into values. Acceptance criteria.  A ConfigMap key can be populated from a file shipped with the chart/tenant without pasting the file body into values.yaml.",
      "comment_count": 0,
      "comments": []
    }
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-2331"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "MZCLD-2331"
      }
    },
    "blocked": true
  }
]

log