Produce machine-consumable output if indicated
Metadata
Current evaluation
Superseded by #183, which added CHARMCRAFT_AUTH for programmatic authentication rather than a global --json-output option.
Resolution: closed superseded
Reason: The maintainer commented that programmatic-use work was being centralized in #183, after which #306 was closed. #183 delivered CHARMCRAFT_AUTH support, but the requested machine-readable output for all messages remained unimplemented.
Evaluated by: mr-cal-bot
No scores available.
Issue body
We should have a `--json-output` or similar option, so all "info or error" output is produced in a json structure.
This way when `charmcraft` is used from scripts or something, those will not need to parse error/success messages (that may slightly change).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Superseded by #183, which added CHARMCRAFT_AUTH for programmatic authentication rather than a global --json-output option. | |
| stealth/space-bunny-alpha | — | closed superseded | JSON output was not implemented; the maintainer centralized programmatic-use support in charmcraft#183, which instead added token authentication via CHARMCRAFT_AUTH. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by pull request #183, which implements the requested machine-consumable JSON output for script integration. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded by PR #183, which centralizes the requested JSON output feature for machine-consumable script integration. The original flag request was merged into a broader implementation. | |
| qwen/qwen3.6-35b-a3b | — | — | Requested a --json-output flag for machine-readable output. The issue was closed and superseded by #183, which centralizes the implementation of machine-consumable output formatting. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by #183, which centralizes the implementation of machine-consumable JSON output. The requested --json-output flag is being handled through that unified effort. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
canonical/charmcraft#183
(confidence 100%)
The maintainer explicitly redirected programmatic-use support to #183, although its JSON-output scope was not completed.
Related issues
No related issues found above the similarity threshold.