← Back to issue list

charmcraft login could list charms and statuses

View original Github issue

Metadata

Project
charmcraft
Number
#192
Type
issue
State
closed
Author
markshuttle
Labels
—
Created
Updated
Closed

Current evaluation

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.

Resolution: closed not a bug

Reason: Maintainer facundobatista closed the request on 2021-01-13 with no code change, noting most commands auto-login so `login` should only authenticate (useful when automating). The behaviour is working as designed; no PR or commit implements the listing.

Evaluated by: mr-cal-bot

No scores available.

Issue body

It would be nice if login provided a bit more information about the status of the account and charms managed by it, perhaps equivalent to snapcraft/charmcraft list. For example: ``` $ charmcraft login Logged in as 'conan'. No charms registered. ``` Or ``` $ charmcraft login Logged in as 'conan'. Name Since Visibility Tracks Notes magmats 2016-10-07 public 0 - asciinema 2017-01-16 public 3 - babeld-dfgafl 2018-07-14 public 1 - ```

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed not a bug 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.
stealth/space-bunny-alpha — closed not a bug Rejected: Charmcraft kept login lightweight because other commands auto-login; direct users likely want only authentication.
qwen3.6-35b-a3b-mtp-q6 — — Rejected. Maintainer explained the login command is rarely used directly due to auto-login features, making extra account queries unnecessary, especially for automation.
qwen/qwen3.6-35b-a3b — — The request to display account and charm status after login was closed and rejected. Maintainers noted the command is rarely used due to auto-login functionality, making additional queries unnecessary, especially for automation.
qwen/qwen3.6-35b-a3b — — The request to display account and charm status after charmcraft login was rejected. A maintainer noted the command is rarely used directly due to auto-login, making extra output unnecessary, especially for automation.
qwen/qwen3.6-35b-a3b — — Rejected. The login command is rarely used due to built-in auto-login, making additional account queries unnecessary for automation. No implementation planned.
qwen3.6-35b-a3b-mtp-q6 — — Rejected. The login command is rarely used due to auto-login features, making extra account or charm output unnecessary, especially for automation. The request was closed without implementation.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#668 `charmcraft status` should work without needing to log in charmcraft closed 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.
76%
#759 charmcraft login produces an error charmcraft closed Closed as superseded by #833, which improved the double-login error and recommended `charmcraft logout`; the follow-up was resolved by merged PR #916.
74%
#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.
71%
#191 charmcraft logout doesn't tell you if you were logged out charmcraft closed Fixed in Charmcraft 1.5 by the craft-store migration: logout now distinguishes an already logged-out state; PR #565 was merged as 70ba8e28.
70%