Implement `charmcraft status <charmname>`
Metadata
Current evaluation
Left unimplemented by Store design: the API prevented the requested status lookup, so discussion moved to snapstore-server#1933250 and the request was closed.
Resolution: closed not a bug
Reason: On 2021-07-06, a maintainer explained that the behavior was intentional Store design and that Snapcraft behaved similarly because of the Store API. Store-side support was tracked separately in Launchpad bug 1933250.
Evaluated by: mr-cal-bot
No scores available.
Issue body
It feels like it would be natural to be able to query the status of any given charm with:
`charmcraft status <charm>`
The results might depend on permissions, handling the situations where:
- the charm name is not registered
- the charm name is reserved
- the charm name is registered but you don't have permission to see status
- it's your charm and you can status if you want to
Note that `snapcraft status <snapname>` works as described.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Left unimplemented by Store design: the API prevented the requested status lookup, so discussion moved to snapstore-server#1933250 and the request was closed. | |
| stealth/space-bunny-alpha | — | closed not a bug | Feature request closed without implementation after maintainers cited Store API restrictions; discussion moved to Launchpad snapstore-server bug #1933250. | |
| stealth/space-bunny-alpha | — | closed not a bug | Feature left unimplemented: Store API restrictions prevented charm status lookup. Discussion moved to Launchpad bug 1933250, and the issue was closed by design. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Feature request for charmcraft status was closed. Implementation depends on Store API support restricted by design. Discussion was redirected to a Launchpad bug report, leaving the feature unimplemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Feature request to add charmcraft status <charm> was rejected. The Store API lacks per-charm status endpoints, matching Snapcraft's behavior. Discussion was redirected to a Launchpad bug report pending upstream API changes. | |
| qwen/qwen3.6-35b-a3b | — | — | Rejected due to Store API design constraints. Maintainers clarified Snapcraft lacks equivalent functionality and redirected discussion to a Launchpad bug. The request was closed without implementation. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected and closed. Implementation requires Store API support, which is unavailable by design. Snapcraft does not function as described. Discussion was redirected to a Launchpad bug report, and the request was abandoned. |
Update history
No update history recorded yet.
Related work
-
Blocked By:
snapstore-server#1933250
(confidence 99%)
Store support was required to provide the requested status information.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #93 Store status | charmcraft | merged | Merged Store status support via canonical/charmcraft#93 in commit 4fca7448, after two approvals. | |
| #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. |