charmcraft release doesn't pay attention to resources
Metadata
Current evaluation
Closed 2021-11-17 without a charmcraft fix: maintainers agreed resource validation belongs in Charmhub, tracking it as Launchpad snapstore-server bug #1951271.
Resolution: closed superseded
Reason: Maintainer facundobatista closed the issue on 2021-11-17 stating the check "is better done Charmhub side", with the request moved to snapstore-server bug #1951271. No client-side validation commit exists in charmcraft's history for this.
Evaluated by: mr-cal-bot
No scores available.
Issue body
I have a charm with an oci-image that I'm using for testing sidecar charms.
I did:
```
charmcraft build
charmcraft upload ./jam-k8s-api-sidecar-test.charm
charmcraft release -r 1 -c stable
```
And it happily let me do so. But now I have a sidecar charm that references a resource that doesn't exist.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Closed 2021-11-17 without a charmcraft fix: maintainers agreed resource validation belongs in Charmhub, tracking it as Launchpad snapstore-server bug #1951271. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed without a charmcraft fix: maintainers agreed resource validation belongs on the Charmhub side; tracked in snapstore-server bug #1951271. | |
| stealth/space-bunny-alpha | — | closed superseded | charmcraft release let a sidecar charm reference a nonexistent resource; maintainers closed it as a Charmhub-side concern, tracked externally in snapstore-server bug #1951271, with no charmcraft code change. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed without a charmcraft fix: maintainer @facundobatista (2021-11-17) decided resource validation belongs Charmhub-side, tracking it in launchpad snapstore-server#1951271. charmcraft `release` still only forwards --resource name:revision to the Store. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as not a charmcraft bug: maintainer (facundobatista) decided resource existence should be validated by Charmhub, not charmcraft; tracked in snapstore-server bug 1951271. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed in favor of Charmhub-side resource validation; the request was tracked in snapstore-server#1951271 rather than implemented in charmcraft. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by a Charmhub backend validation request. Resource validation for releases is deferred to the server side. A new bug was opened to track the snapstore-server fix. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a client-side fix. Resource validation was deferred to the Charmhub server side. A separate Launchpad bug was opened to track the server-side implementation. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. Resource validation deferred to Charmhub server side rather than charmcraft. A new bug was opened to track server-side enforcement during release. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a charmcraft fix. Resource validation was deferred to the Charmhub backend, with tracking moved to a new Launchpad issue. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
snapstore-server#1951271
(confidence 85%)
Launchpad bug opened 2021-11-17 to track Charmhub-side resource validation, cited in the closing comment.
-
Related To:
canonical/charmcraft#457
(confidence 40%)
Merged PR (b5d735b4) added --resource to upload --release, addressing attaching resources at release time but not validating resource names.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #850 charmcraft release failed for revision that is in the charmhub | charmcraft | closed | Closed as out of scope: Charmhub auto-release exposed charm revisions missing released resource revisions; responsibility was moved to the Launchpad–Charmhub integration, with no Charmcraft code fix. | |
| #354 Charmcraft release should be able to attach a resource during revision creation | charmcraft | closed | Closed as abandoned on 2021-07-21 after the maintainer could not reproduce the failure and received no follow-up. | |
| #1435 `charmcraft release` doesn't use output text from the store. | charmcraft | open | charmcraft release ignores Charmhub's response and prints resource details from CLI arguments, potentially reporting a different revision than was attached; no fix or maintainer response is recorded. | |
| #4266 Charmcraft no longer builds from scratch using edge release of snapcraft | snapcraft | closed | Closed as stale without a Snapcraft fix; Charmcraft PR #1146 proposed a workaround but was closed unmerged because it broke stable Snapcraft. | |
| #672 charmcraft 1.4.0: impossible to login to charmhub | charmcraft | closed | Closed as intended behavior: the headless remote host had no local keyring, so Charmcraft could not persist credentials; exporting credentials was the supported workaround. | |
| #847 Improve the 'release' response when resources are automatically released with the charm | charmcraft | open | Enhance charmcraft release output to list resources Charmhub automatically attaches; the backend fix is available, but current output only reports resources passed with --resource. |