Update `charmcraft status charmname --format json` output terminology
Metadata
Current evaluation
Resolved by merged PR #802 (commit 74dcf904): status JSON now uses "mappings" and preserves the full track in channel values.
Resolution: closed resolved
Reason: PR #802 was merged as commit 74dcf904, renaming the outer "channels" key to "mappings" and fixing channel values to include the full track.
Evaluated by: mr-cal-bot
No scores available.
Issue body
An example (truncated) output from `charmcraft status metacontroller-operator --format json` is given by:
```
charmcraft status metacontroller-operator --format json
[
{
"track": "latest",
"channels": [ # <------------ A) Not sure what this should be
{
"base": {
"name": "ubuntu",
"channel": "20.04",
"architecture": "amd64"
},
"releases": [
{
"status": "open",
"channel": "stable", # <---------- B) Should this be "risk"?
"version": "2",
"revision": 2,
"resources": [],
"expires_at": null
},
...
}
]
}
]
},
]
```
The name `channel` is used twice, neither of which afaik describes a channel ([snapcraft definition](https://snapcraft.io/docs/channels), [charmhub definition](https://discourse.charmhub.io/t/channel/6562). Pointing to the letters added above:
* A) I'm not sure what this would be, but I don't think it is a channel because it excludes `track`
* B) I think this is `risk`, not a `channel`
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Resolved by merged PR #802 (commit 74dcf904): status JSON now uses "mappings" and preserves the full track in channel values. | |
| stealth/space-bunny-alpha | — | closed resolved | PR #802 was merged, renaming the status JSON “channels” key to “mappings” and fixing channel values to include the full track, resolving both reported concerns. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The charmcraft status JSON output terminology was updated. The channels key was renamed to mappings, and a bug causing the channel field to omit the track was fixed. Resolved via PR 802. | |
| qwen/qwen3.6-35b-a3b | — | — | The charmcraft status JSON terminology was updated by renaming channels to mappings and fixing a related channel field bug. The issue was closed after the maintainer merged fix PR 802. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved confusing JSON output terminology by renaming channels to mappings and fixing a missing track in the channel field. Both issues were addressed and merged in PR #802. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#802
(confidence 100%)
Merged PR implementing both terminology and full-track fixes requested in #799.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #933 Update the charmcraft status --format | charmcraft | merged | Merged in canonical/charmcraft#933, commit 2f673059, clarifying that charmcraft status --format supports JSON only and fixing #794. YAML support was removed and split into #940. | |
| #802 Improve json format for the status command. | charmcraft | merged | Merged PR #802 (aaec4e23), replacing status JSON "channels" with "mappings" and retaining full track-qualified channel names; fixes #799. | |
| #794 Clarify `charmcraft status --help` text for `--format` | charmcraft | closed | Clarified `charmcraft status --format` help to state that it accepts `json`; merged via #933 (commit `2f673059`). |