Description
otdfctl profile get <name> --json (or otdfctl --json profile get <name>) exits with code 0 but produces no stdout output.
Steps to Reproduce
otdfctl profile create my-profile https://platform.opentdf.local:8443
otdfctl profile get my-profile --json
# or
otdfctl --json profile get my-profile
Current Behavior
- Exit code: 0
- Stdout: empty
Expected Behavior
Either:
- Valid JSON output representing the profile, or
- A non-zero exit code with an error message if JSON rendering is not supported for this command
Why It Matters
Exit 0 + empty stdout is indistinguishable from "this profile has no data." Any script or tool that relies on --json output from profile get will silently get nothing, which is harder to debug than an explicit error. It also means the --json flag is effectively broken for this command.
Context
Discovered while testing the OpenTDF quickstart docs. Related to #761 -- (see companion issue about tlsNoVerify not being displayed).
Description
otdfctl profile get <name> --json(orotdfctl --json profile get <name>) exits with code 0 but produces no stdout output.Steps to Reproduce
otdfctl profile create my-profile https://platform.opentdf.local:8443 otdfctl profile get my-profile --json # or otdfctl --json profile get my-profileCurrent Behavior
Expected Behavior
Either:
Why It Matters
Exit 0 + empty stdout is indistinguishable from "this profile has no data." Any script or tool that relies on
--jsonoutput fromprofile getwill silently get nothing, which is harder to debug than an explicit error. It also means the--jsonflag is effectively broken for this command.Context
Discovered while testing the OpenTDF quickstart docs. Related to #761 -- (see companion issue about tlsNoVerify not being displayed).