Add command line options to charmcraft upload to enable publishing the charm and its resources with a single command run
Metadata
Current evaluation
Maintainers declined atomic creation of a charm and new resources in one command, recommending an external script; no PR or commit implemented #840.
Resolution: closed not a bug
Reason: In the 2022-08-25 closing discussion, facundobatista explained that Charmhub's two-stage transfer-and-commit API made combined uploads complex and potentially wasteful, recommending an external script using Charmcraft's programmatic output. No resolving PR or commit was recorded.
Evaluated by: mr-cal-bot
No scores available.
Issue body
It would be nice to have a way to publish in a single `charmcraft upload` run the charm and its resources for those cases in which they share the life-cycle to prevent versioning issues, improve developer experience and minimize the existence of dangling resources when the charm upload fails in CI when the previous steps are successful.
From a developer's perspective, what I have in mind is to support specifying the current ùpstream-source`parameter in the metadata file in the command line interface, so that, when present, the command will create the resources along with the charm, although better options might exist.
Thank you!
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Maintainers declined atomic creation of a charm and new resources in one command, recommending an external script; no PR or commit implemented #840. | |
| stealth/space-bunny-alpha | — | closed not a bug | Feature request for single-run charm+resource upload declined by maintainer; closed with advice to use existing --release/--resource options or an external script using Charmcraft's programmatic (JSON) output. | |
| stealth/space-bunny-alpha | — | closed not a bug | Declined without implementation; maintainers recommended coordinating resource and charm uploads through an external script using Charmcraft's programmatic outputs. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to atomically upload charms and new resources was declined. Maintainers cited complexity and Charmhub's two-step upload inefficiency, recommending external scripts instead. The issue was closed without implementation. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
60
Confidence:
90
Support Request:
10
|
close not a bug | Feature request to upload charms and new resources in a single CLI command. Maintainer declined due to architectural constraints and complexity, suggesting external scripting. Inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
78
Confidence:
85
Support Request:
5
|
close stale | Feature request to upload charms and new resources in a single CLI command. Maintainer raised architectural concerns and suggested external scripting. Inactive for over a year, unlabelled. |
Update history
| Date | Change |
|---|---|
| closed |
Related work
-
Related To:
canonical/charmcraft#457
(confidence 95%)
Merged as b5d735b4 and shipped in 1.1.2; it added upload --release resource support, but did not create and commit new resources atomically.
-
Related To:
canonical/charmcraft#1979
(confidence 90%)
A later open request covering a remaining upload-and-resource automation gap; it confirms that --release already exists.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #126 Add a "--release" option to the "upload" command | charmcraft | closed | Implemented charmcraft upload --release in canonical/charmcraft#255 (merge 9064a3f3, feature bc06a62a); #457 added resource support and shipped in Charmcraft 1.1.2. |