Skip to content

feat(EPINIO-819): add push_appchart for OCI chart uploads - #6

Open
psanghvi17 wants to merge 1 commit into
mainfrom
feat/epinio-819-appchart-push
Open

psanghvi17 wants to merge 1 commit into
mainfrom
feat/epinio-819-appchart-push

Conversation

@psanghvi17

Copy link
Copy Markdown
Contributor

Expose Epinio's appchart push API on MCP so agents can upload chart archives to the registry, and clarify create/update/delete guidance around pushed charts.

What changed

  • Added client.PushAppChart for POST /api/v1/appcharts/push (multipart archive upload).
  • Added MCP tool push_appchart (base64 chart archive, optional base64: prefix, 8 MiB decoded size cap).
  • Clarified create_appchart / update_appchart / delete_appchart descriptions for pushed vs reference-based charts (behavior unchanged).
  • Documented chart_write permission on create/push tool descriptions.
  • Unit tests for the client method, archive decode, and push tool helper.

Why

Epinio already supports OCI appchart push. MCP had create-by-reference and delete, but no way to upload a chart archive into Epinio's registry.

EPINIO-819

What to test

  1. Run make check.
  2. Call push_appchart with a valid base64 .tgz and a new name → AppChart created; show_appchart shows an oci://… helm chart in Epinio's registry.
  3. Call push_appchart again with the same name while unused → chart replaced.
  4. Call create_appchart / update_appchart / delete_appchart as before → still work; delete of a pushed chart also removes it from the registry.
  5. push_appchart / create_appchart without chart_write → denied by Epinio.

Possible regressions

Existing create/update/delete API calls are unchanged; only tool descriptions were clarified. Adjacent area to spot-check: other multipart upload tools that share the client upload helper.

Type

feature

Checklist

  • make check passes (fmt-check, vet, lint, test)
  • New or changed behavior has tests, or the test impact is noted above
  • Tool names, inputs, or outputs changed? The MCP server reference is updated
  • New or changed capability sits in the right tier: core (Epinio API only, runs as the caller) vs elevated (EPINIO_MCP_ELEVATED, reaches directly into Kubernetes and needs the standard-elevated RBAC)
  • Touches auth, credentials, or the RBAC/appchart surface? Flagged for security review
  • User-facing behavior changed? A matching PR is opened in epinio/docs
  • No secrets, tokens, or real cluster credentials committed

Expose Epinio's appchart push API on MCP so agents can upload chart archives to the registry, and clarify create/update/delete guidance around pushed charts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant