That's awesome. Support Teams could benefit this a lot. Also it's a real benefit to do not put hardcored log instructions in the code 👍. Although for all log systems I always feel it's like a backdoor. Backend and databases have a lot of private informations and fortunately we have solutions to hide them: - One of the reason we use Password's Salting is to disable anyone, malicious employee included, to see users/customers passwords - we have Secrets to prevent anyone to access critical databases and so private informations With this I can log the login module, and more precisely the request containing the password in clear, so understand the unhashed password of a specific user before it get hashed for comparison with the salted/hashed password in database. Isn't it? Or maybe hashed the password in the frontend before the backend request. 🤷♂️ I hope at least the LeadDev/Maintainer/CTO/CIO can ban some line of codes or portion of modules to be logged. Hope also that the product include an history of who had log code and when it has been done. Also policy and some sort of Form to keep note of authorization given by a user when a Support Employee access some private informations.
Thanks for the information. Very helpful. I am just wondering about code review process using Google Cloud Source Repositories. Because git and bitbucket has nice GUI to raise Pull Request, Code Review and Merge process if everything looks. Will it be possible to do the same using CSR? Please let me know.
