Overview
This epic tracks the implementation of roadmap section 12: Add JSON output format to all commands, with the goal of making JSON the default output format once complete.
New Decision: JSON as Future Default
Once all commands support JSON output, the default will switch from text to json. This prioritizes AI agent and automation UX over human UX — human UX is increasingly the use of AI agents.
The switch to JSON default cannot happen until all commands are implemented (otherwise the application panics for unimplemented commands).
Roadmap Reference
From docs/roadmap.md - section 12:
Add machine-readable JSON output format to all commands to improve automation and AI agent integration. Once all commands support JSON output, JSON will become the default format.
Context: JSON output enables programmatic parsing, making it easier for scripts and AI agents to extract specific information (like IP addresses, service URLs, environment names) without parsing human-readable text.
Specification
See detailed specification: docs/issues/348-epic-add-json-output-format-support.md
Tasks
Phase 1 - High-Value Commands ✅ Completed
Phase 2 - Remaining Commands
(Task issues will be created and linked as work progresses)
Related
Overview
This epic tracks the implementation of roadmap section 12: Add JSON output format to all commands, with the goal of making JSON the default output format once complete.
New Decision: JSON as Future Default
Once all commands support JSON output, the default will switch from
texttojson. This prioritizes AI agent and automation UX over human UX — human UX is increasingly the use of AI agents.The switch to JSON default cannot happen until all commands are implemented (otherwise the application panics for unimplemented commands).
Roadmap Reference
From docs/roadmap.md - section 12:
Specification
See detailed specification: docs/issues/348-epic-add-json-output-format-support.md
Tasks
Phase 1 - High-Value Commands ✅ Completed
createcommandprovisioncommandshowcommandruncommandlistcommandPhase 2 - Remaining Commands
configurecommand #371 -configurecommand (12.6)releasecommand #377 -releasecommand (12.7)testcommand #380 -testcommand (12.8)destroycommand (12.9) #386 -destroycommand (12.9)validatecommand (12.10) #390 -validatecommand (12.10)rendercommand (12.11) #392 -rendercommand (12.11)purgecommand (12.12) #394 -purgecommand (12.12)registercommand (12.13) #396 -registercommand (12.13)texttojson(12.14) #398 - Switch default format fromtexttojson(12.14)(Task issues will be created and linked as work progresses)
Related