← Back to issue list

Support for charms' resources

View original Github issue

Metadata

Project
charmcraft
Number
#176
Type
issue
State
closed
Author
facundobatista
Labels
—
Created
Updated
Closed

Current evaluation

Resource support was completed by merged PRs #252, #253, #259, and #262, covering listing, uploading, release attachment, and status output.

Resolution: closed resolved

Reason: Merged canonical/charmcraft#252 (fbd67a97) added resource listing, #253 (f23482c8/ed071757) added uploads, #259 (35855e58) added release attachment, and #262 (eb11a844) added status details. Together these implement all operations requested in #176.

Evaluated by: mr-cal-bot

No scores available.

Issue body

We need to support the resources of the charms, interacting with the Store properly for all these related operations. In detail: - there's no "resource registration", as resources are declared in the `metadata.yaml` file (after a charm is uploaded indicating that has some resources in that file, the Store will allow the author to manage those resources). - list the resources for the charm (using store's [`list_resources`](https://api.staging.charmhub.io/docs/default.html#list_resources) endpoint). - upload a new resource (using store's [`push_resource`](https://api.staging.charmhub.io/docs/default.html#push_resource) endpoint. - to release resources and list those released resources, we need to improve the `release` command (as resources are incorporated in the [release](https://api.staging.charmhub.io/docs/default.html#release) endpoint) and the `status` command (because now the [list_releases](https://api.staging.charmhub.io/docs/default.html#list_releases) endpoint includes the resources information in the channelmap field).

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Resource support was completed by merged PRs #252, #253, #259, and #262, covering listing, uploading, release attachment, and status output.
stealth/space-bunny-alpha — closed resolved Charm resource support was completed by merged PRs #252, #253, #259 and #262, covering listing, uploading, release integration and status output.
qwen3.6-35b-a3b-mtp-q6 — — Closed without implementation. The feature request to manage charm resources via the Store API remains unaddressed, likely abandoned or superseded. No comments or resolution details were provided.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The charm resource support feature request was abandoned due to inactivity. No resolution, merge, or superseding PR was created.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The feature request for charm resource management via the Store API was abandoned.
qwen3.6-35b-a3b-mtp-q6 — — Closed without implementation. The charm resource management feature request remains unaddressed and appears abandoned or superseded by subsequent work.

Update history

No update history recorded yet.

Related work

Related issues

Issue Project State Summary Similarity
#262 Support resources when showing charm status. charmcraft merged Merged PR #262 (commit eb11a844) added resource revision details to charm status output, completing resource support tracked in #176.
82%
#259 Support for attaching resources when releasing charms. charmcraft merged Merged PR #259 in commit 35855e58, adding resource attachment support when releasing charms through the upload command.
80%
#457 Allow including resources when releasing charms directly in the upload command (CRAFT-381). charmcraft merged Merged PR #457 (b5d735b4), adding --resource support to upload --release and fixing #456; the fix shipped in Charmcraft 1.1.2.
75%
#253 Support for resource uploading charmcraft merged Merged resource-uploading support in canonical/charmcraft#253 via commit f23482c8 and merge commit ed071757.
73%
#2172 docs: update release step with resource details charmcraft merged Merged documentation PR #2172 in commit df9125d6, adding resource-attachment details and consistent charm naming to the Charmhub release example; it fixes #2171.
70%