Description
otdfctl profile get <name> does not display the tlsNoVerify field in its output, even though the value is stored in the profile config and has a meaningful effect on behavior.
Steps to Reproduce
otdfctl profile create --tls-no-verify my-profile https://platform.opentdf.local:8443
otdfctl profile get my-profile
Current Behavior
The table output shows: Profile, Endpoint, Is default, Output format, Auth type — but no TLS verification field.
Expected Behavior
profile get should show whether tlsNoVerify is enabled, e.g. as a "TLS Verify" or "Skip TLS Verify" column/field.
Why It Matters
--tls-no-verify on profile create persists TLSNoVerify: true to the profile config, which silently affects all subsequent commands (encrypt, decrypt, auth, etc.). Without visibility into this setting, users have no way to confirm it was saved, making TLS issues hard to diagnose ("did I create this profile with the flag or not?").
Context
Discovered while testing the OpenTDF quickstart docs with a self-signed cert and no trusted CA.
Description
otdfctl profile get <name>does not display thetlsNoVerifyfield in its output, even though the value is stored in the profile config and has a meaningful effect on behavior.Steps to Reproduce
Current Behavior
The table output shows: Profile, Endpoint, Is default, Output format, Auth type — but no TLS verification field.
Expected Behavior
profile getshould show whethertlsNoVerifyis enabled, e.g. as a "TLS Verify" or "Skip TLS Verify" column/field.Why It Matters
--tls-no-verifyonprofile createpersistsTLSNoVerify: trueto the profile config, which silently affects all subsequent commands (encrypt,decrypt,auth, etc.). Without visibility into this setting, users have no way to confirm it was saved, making TLS issues hard to diagnose ("did I create this profile with the flag or not?").Context
Discovered while testing the OpenTDF quickstart docs with a self-signed cert and no trusted CA.