Replies: 1 comment 2 replies
|
Good catch. There is no strong product reason for that difference. Since The only caveat is that secrets often appear inside code, JSON, env files, shell commands, etc., so adding the marker can make restored output invalid. But because the option is disabled by default, that tradeoff is acceptable for explicit debug/demo use. I will make this consistent in a PR. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
As the title says. PII data shows [protected] before the data entry in response.
Why not with secrets?
@sgasser
All reactions