Skip to content

EPIC: Add JSON output format support #348

@josecelano

Description

@josecelano

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

  • Add JSON output format to configure command #371 - configure command (12.6)
  • release command (12.7)
  • test command (12.8)
  • destroy command (12.9)
  • validate command (12.10)
  • render command (12.11)
  • purge command (12.12)
  • register command (12.13)
  • Switch default format from text to json (12.14)

(Task issues will be created and linked as work progresses)

Related

Sub-issues

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions