Add command line options to charmcraft upload to enable publishing the charm and its resources with a single command run
Metadata
Current evaluation
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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
60
Confidence:
80
Support Request:
10
|
close not a bug | Proposes adding CLI options to charmcraft upload for publishing new charm resources alongside the charm in one command. Maintainer suggests external scripting, citing backend API limits and upload inefficiency for atomic commits. Status remains open under discussion. |
Update history
| Date | Change |
|---|---|
| closed |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #839 Upload resources on charmcraft upload when specified as upstream-resource in the metadata file | charmcraft | closed | Rejected. Maintainers declined automatic resource uploads to prevent copying third-party images to Canonical's registry and avoid inefficient uploads. Developers should script the process using Charmcraft's CLI. |