You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to pyinfra, trying to rewrite MySQL user management from Ansible, when I try to add some verbosity to understand what is going on (-v flag) I am seeing mysql_password in plain text all over the logs.
mysql is probably not the only place that doesn't sanitize secretd like this.
To Reproduce
Connect to password-protected MySQL database with -v flag.
Expected behavior
I would expect all possibly sensitive information to be masked out from logging, unless (or even when) I use the maximum verbosity. It cloud go as far as using separate flag like --debug-secret to unmask those.
This is unfortunate. A lot of work went into the MaskString and various string command classes, unfortunately fact arguments are bypassing that entirely.
Describe the bug
I'm new to
pyinfra
, trying to rewrite MySQL user management from Ansible, when I try to add some verbosity to understand what is going on (-v
flag) I am seeingmysql_password
in plain text all over the logs.mysql
is probably not the only place that doesn't sanitize secretd like this.To Reproduce
Connect to password-protected MySQL database with
-v
flag.Expected behavior
I would expect all possibly sensitive information to be masked out from logging, unless (or even when) I use the maximum verbosity. It cloud go as far as using separate flag like
--debug-secret
to unmask those.Meta
in pyinfra
2.9.2
@Fizzadar mentioned on Matrix chat:
The text was updated successfully, but these errors were encountered: