charmcraft login could list charms and statuses
Metadata
Current evaluation
Rejected. Maintainer explained the login command is rarely used directly due to auto-login features, making extra account queries unnecessary, especially for automation.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. Maintainer declined the feature, noting auto-login handles most authentication and automation workflows should avoid unnecessary queries. The issue 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 as rejected. Maintainer confirmed all Charmhub operations require authentication, making the requested unauthenticated status check impossible to implement within charmcraft. | |
| #190 charmcraft whoami tries to login | charmcraft | closed | Closed without resolution, likely abandoned. The charmcraft whoami command incorrectly triggered a login flow when unauthenticated instead of displaying a not logged in status. | |
| #672 charmcraft 1.4.0: impossible to login to charmhub | charmcraft | closed | Closed as expected behavior. Charmcraft falls back to a non-persistent memory ring on headless systems lacking a keyring, preventing credential persistence. Maintainers advised exporting credentials via environment variables instead of implementing a code fix. |