Skip to main content
← Back to list
01Issue
BugOpenSwamp CLI
AssigneesNone

Relationships

#646 vault read-secret mixes log output into stdout

Opened by bixu · 6/13/2026

Summary

swamp vault read-secret <vault> <key> --force writes a structured log line to stdout alongside the secret value, on the same line. This makes the command unusable in shell substitution ($(swamp vault read-secret ...)) because the captured value includes the log prefix.

Repro

swamp vault read-secret myvault mykey --force 2>/dev/null | od -c | head -3

Expected: only the secret value on stdout, log lines on stderr.

Actual: stdout contains a single line like 10:00:15.092 INF vault·read-secret "the_actual_secret_value" — the log timestamp, level, and component are prepended to the secret.

Impact

Any script or CI pipeline that captures the secret via $() gets garbage (log prefix + secret) instead of the raw secret. Workaround: parse the secret out with grep -o, but this is fragile and depends on the key format.

Expected behavior

vault read-secret should write only the secret value to stdout. Log output should go to stderr (or be suppressed entirely when --force is used).

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

6/13/2026, 10:05:00 AM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.