drush-ops
Add sanitization for dblog
Database log entries may contain user-related information, such as debug data. In use cases, where sanitization is used when importing prod db to staging environments, it may not be as relevant to include log entries from different environments.
We could add a command that takes care of that, but for BC make it opt-in.
If maintainers think this makes sense, I could create a PR for this.
I would consider this is plain drupal core enters sensitive info into the logs. If it takes contrib or custom code to do it, I dont think Drush core needs to handle it.
the watchdog table contains IP's, that many any log entry connected to a user personal.
