- Issue created by @omarlopesino
- 🇮🇳India nikunjkotecha India, Gujarat, Rajkot
This looks great but probably a final solution, to begin with let's implement hook_alter in below files before we actually log so developers can add code to sanitise fields they want and in a way they want (full / partial / etc.) ?
If you agree we can keep this ticket as is and add the smaller scope in another ticket. This ticket would be really handy for people not doing any code or very little code, however projects interested in logs are mostly developer friendly projects :)
- 🇨🇭Switzerland florianmuellerch Aarau, Switzerland
The most important aspect in my case is that it is configurable weather to redact any information at all, and maybe even what info to redact.
For example, I could have use cases where I want to protocol sensitive actions, where I fully need the info such as full emails, maybe even credit card numbers for legal reasons for a certain amount of time. The responsibility should lie with the site maintainer. We could opt for a setting "Redact sensitive information" that defaults to true, but is still disableable. - 🇪🇸Spain omarlopesino
Thanks both for the feedback!
About #1: Adding a hook will allow developers quickly sanitizing the values, meanwhile we prepare a definitive solution. It would also let developers add custom logic to the redaction, as maybe it needs some dynamic calculation, or a specific way to redact it.
This approach would help users less familiarized with module development / those who want to provide this redact configuration through recipes.
I will open a new issue for adding the hooks to alter diffs, independent on the purpose.
About #2: I agree as it will help to easily switch on and off the redaction. That can be saved into Drupal state, so it does not need deployments.