When not using debug-level logging, Plax doesn't (or shouldn't) log bindings values, payloads, or some other potentially sensitive data. However, when running in a CI context, it's nice to have debugging output to help diagnose problems that might only occur in the CI context (without having to jump into that context and attempt to re-run tasks with increased logging). So it'd be nice to have the option to redact certain values redacted from logging output.
References
Concourse has some gear for redacting credentials. Note that those heuristics are imperfect and CPU-expensive.
When not using debug-level logging, Plax doesn't (or shouldn't) log bindings values, payloads, or some other potentially sensitive data. However, when running in a CI context, it's nice to have debugging output to help diagnose problems that might only occur in the CI context (without having to jump into that context and attempt to re-run tasks with increased logging). So it'd be nice to have the option to redact certain values redacted from logging output.
References