Support `charmcraft info` for charmhub details for a charm name
Metadata
Current evaluation
Closed as superseded: charm info lookup was assigned to Juju (`juju info`), keeping developer/consumer tools split like snapcraft/snap. A later request for the command (#404) was closed as a duplicate of this issue.
Resolution: closed superseded
Reason: Per facundobatista's closing comment (2021-01-19) and sergiusens' note that Juju would adopt the functionality (2021-01-18), charmhub charm details are served by `juju info`, not charmcraft; the follow-up issue #404 was closed by maintainer facundobatista as a duplicate of #187.
Evaluated by: mr-cal-bot
No scores available.
Issue body
The `snap info <foo>` command is very useful. I think it would make sense to have the same command in both juju and charmcraft. Am not sure what the plan is with the current `charm` command but I suspect most of that functionality will come to charmcraft. It might be nice to think about using the `charm` command to interact with charms in the model, potentially.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Closed as superseded: charm info lookup was assigned to Juju (`juju info`), keeping developer/consumer tools split like snapcraft/snap. A later request for the command (#404) was closed as a duplicate of this issue. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed as superseded: charm information functionality was assigned to Juju, while Charmcraft remained developer-focused; later request #404 was closed as a duplicate. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as superseded. The requested functionality will be implemented in Juju instead, as the team determined it belongs in consumer-side tooling rather than the developer-focused charmcraft suite. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded. The charmcraft team decided Juju will adopt the charm info functionality instead, keeping developer and consumer tooling separate. The request was closed without implementation in charmcraft. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to add charmcraft info for fetching Charmhub details was declined. The team determined this belongs on the consumer side, and Juju will adopt the functionality instead, keeping developer and consumer tooling separate. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as superseded. The charmcraft info feature was deferred to Juju, which will adopt the functionality to keep consumer and developer tooling separate. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
canonical/charmcraft#404
(confidence 88%)
`charmcraft info` command request closed as a duplicate of #187, confirming the decision not to implement the command in charmcraft.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #404 `charmcraft info` command | charmcraft | closed | Closed by maintainer facundobatista as a duplicate of #187; the team decided charm/store info lookup belongs to `juju info` (like snapcraft/snap), so no `charmcraft info` command was added. |