[ehl-jf]

Summary

Adds opt-in JSON output for HTTP error responses across the entire CLI. When enabled, any command that hits the platform — Artifactory, Access, Xray, Pipelines, OIDC token exchange — emits a structured JSON object on stdout (the data channel) instead of human-readable text on stderr. Default behavior is unchanged; this is purely additive.

How to use

Two equivalent triggers:

Mechanism	Example
Environment variable	JFROG_CLI_ERROR_OUTPUT_FORMAT=json jf rt ping ...
--format=json auto-promote	jf rt ping --format=json ...

If both are set, the env var wins. Any value other than json (or unset) keeps the current text behavior.

Channel contract (JSON mode)

Stream	Contents
stdout	parseable JSON: {status_code, status, body} — body is a nested object when the server returned JSON
stderr	log lines only ([Info]/[Warn]/Trace ID), unchanged from today
exit	1

Makes jf <cmd> --format=json 1>out.json 2>err.log work cleanly: jq . out.json parses, err.log is for humans.

Coverage

• All commands routing through jfrog-client-go's CheckResponseStatus* (i.e. the standard HTTP error path on every JFrog service).
• OIDC token exchange (jf eot) end-to-end.
• jf api: in JSON mode, the structured error replaces the body-on-stdout dump; in default mode, curl-like behavior is preserved.
• Transport errors (connection refused, TLS) intentionally fall through to the existing text path — there's no HTTP response to wrap.

Companion PR

Depends on jfrog/jfrog-client-go#1345, which exposes the typed HttpResponseError this PR consumes. go.mod is pinned to that branch's pseudo-version; bump to a released version once #1345 merges.

Tests

Unit tests in utils/cliutils/errorformat_test.go (env var precedence, flag auto-promote variants, false-positive guards, legacy-text fallback) and general/api/cli_test.go (JSON-mode emits structured stdout, success path unchanged, default mode still dumps body).

---

• All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• The pull request is targeting the master branch.
• The code has been validated to compile successfully by running go vet ./....
• The code has been formatted properly using go fmt ./....

---

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ (ehl-jf)[https://github.com/ehl-jf]
❌ @actions-user
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}