Discovered during v0.4.2 post-merge stress testing.
cloud org prometheus <id> --json and cloud service prometheus <id> --json accept the flag but silently emit raw Prometheus exposition text (exit 0, not parseable as JSON).
Emitting Prometheus text is the correct behavior (transforming it to JSON would lose the format contract) — but --json being silently accepted is confusing, especially for agent consumers that expect parseable JSON.
Expected
State in the --help text for both commands that --json is ignored / output is always Prometheus text format.
Discovered during v0.4.2 post-merge stress testing.
cloud org prometheus <id> --jsonandcloud service prometheus <id> --jsonaccept the flag but silently emit raw Prometheus exposition text (exit 0, not parseable as JSON).Emitting Prometheus text is the correct behavior (transforming it to JSON would lose the format contract) — but
--jsonbeing silently accepted is confusing, especially for agent consumers that expect parseable JSON.Expected
State in the
--helptext for both commands that--jsonis ignored / output is always Prometheus text format.