`charmcraft status` should work without needing to log in
Metadata
Current evaluation
Closed by facundobatista (2022-02-16) as out of Charmcraft's hands: `status` is backed by Charmhub APIs, which require authentication. No code change made; login remains mandatory.
Resolution: closed not a bug
Reason: The reporter asked for unauthenticated `charmcraft status`, but maintainer facundobatista closed it stating "It's out of `charmcraft` hands, all Charmhub related operations need authentication :(". No commit or PR references issue #668, and the status command remains in the Charmhub 'store' command group whose service calls require a token.
Evaluated by: mr-cal-bot
No scores available.
Issue body
`charmcraft status` returns very basic information, that probably shouldn't require a login:
```
> $ charmcraft status grafana-k8s
Track Base Channel Version Revision Resources
latest ubuntu 20.04 (amd64) stable - - -
candidate - - -
beta 18 18 grafana-image (r2)
edge 20 20 grafana-image (r4)
```
This is useful when debugging on a remote machine.
```
> $ charmcraft status grafana-k8s
Not logged in.
Full execution log: '/home/ubuntu/snap/charmcraft/common/cache/charmcraft/log/charmcraft-20220209-220117.573765.log'
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Closed by facundobatista (2022-02-16) as out of Charmcraft's hands: `status` is backed by Charmhub APIs, which require authentication. No code change made; login remains mandatory. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as expected behavior: `charmcraft status` queries Charmhub, whose operations require authentication; no code change or resolving PR was provided. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as expected behavior: `charmcraft status` accesses Charmhub, whose operations require authentication, according to facundobatista's 2022-02-16 closing comment. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as rejected. Maintainer confirmed all Charmhub operations require authentication, making the requested unauthenticated status check impossible to implement within charmcraft. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The charmcraft team rejected the request, noting all Charmhub API operations require authentication and the limitation is outside charmcraft's control. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. Charmhub requires authentication for all operations, blocking unauthenticated status checks. Closed as the limitation falls outside charmcraft's control. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#844
(confidence 62%)
Another auth-related issue where the remote-machine use case was closed by directing users to Charmhub discourse login instructions; same root constraint (Charmhub-side auth), no code change.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #192 charmcraft login could list charms and statuses | charmcraft | closed | Enhancement request to have `charmcraft login` also list account charms/statuses was declined and closed; maintainer facundobatista argued login is rarely needed due to auto-login and should stay lightweight. | |
| #844 Cannot use charmcraft login | charmcraft | closed | Login failed over SSH ('Prompt dismissed'). Maintainer closed it pointing to Charmhub discourse instructions for authenticating in remote environments; no code change. | |
| #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. | |
| #1652 Allow `charmcraft status anycharm` for everyone | charmcraft | open | Anonymous charmcraft status remains unavailable to non-publishers; the request is unresolved and under discussion after a maintainer raised public-data and API scope questions. | |
| #725 craft-store error when using `charmcraft login` command | charmcraft | closed | Confusing craft-store "Credentials found" error on `charmcraft login` (double login). Closed by facundobatista as tracked in the more specific #833, whose improved error landed via PR #916. |