secretless-broker
secretless-broker copied to clipboard
A mechanism exists to redact sensitive values in logs
Description
It's possible for values like hostname and port to be leaked through error messages. These error messages can make it to the client or end up logs. We need some mechanism for dealing with this.
Here's an issue that attempted to do it in piece-wise fashion for the MSSQL driver https://github.com/cyberark/go-mssqldb/pull/26. It was closes in favour of this issue. We can use this issue to discuss approaches then start work when we've converged on something.