Make explicit that image resources are not uploadable by tag
Metadata
Current evaluation
Superseded by charmcraft 3. The tool now uses explicit --image-id and --image-digest flags, eliminating the ambiguous --image tag handling and resolving the reported UX issue.
Suggested action: —
No scores available.
Issue body
We only support uploading image resources using the image id or its digest, not its tag.
Currently, however, if you write `--image=myrepo:stable` charmcraft thinks that the passed string is a digest, and fails to find it. It should detect that it's a tag and fail with an error like "The --image option must refer to an image id or a digest, not a tag.", to simplify user correction.
Futrthermore, the documentation should explicit that tags are not supported.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by charmcraft 3. The tool now uses explicit --image-id and --image-digest flags, eliminating the ambiguous --image tag handling and resolving the reported UX issue. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded by charmcraft 3, which resolved the image upload ambiguity. The proposed deprecation of --image in favor of explicit --image-id and --image-digest options became unnecessary with the new version. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by charmcraft 3, which resolved the CLI ambiguity. The proposed deprecation of --image in favor of explicit --image-id and --image-digest options was rendered unnecessary by the v3 release. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by charmcraft 3, which replaced the ambiguous --image flag with explicit options. The requested error handling and documentation updates are no longer relevant. Closed as obsolete. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #906 `charmcraft upload-resource` 2.1.0 removes ability to pass tagged image names to `--image` argument | charmcraft | closed | Closed as solved. Affected teams migrated CI to use image digests instead of tags. Rather than reverting the change, PR #912 was created to improve error messaging when tagged image names are provided. | |
| #1953 Charmcraft 3 should still accept image digests for `upload-resource` | charmcraft | open | Charmcraft 3 `upload-resource` rejects bare image digests (e.g. sha256:…) that charmcraft 2 accepted; the ImageService lacks a digest-based lookup via RepoDigests. Unlabeled, no maintainer response, only a bot Jira-sync comment. |