Currently when diverting remote connections on it logs all of the information being sent.
This mean PII is getting into the logs which is something Joshua said not to do, and something we agreed not to do.
This crept in because we originally didn't divert on servers that had real data.
Now that we do we should remove information with PII from any logging and print functions. As side note while removing that information we should switch to using logs in any place that still using print statement, its trivial.
We should also discuss what to do about the logs on both production and staging. This data is currently stored in papertrail and in a bucket in AWS. Its unclear how to empty papertrail
Currently when diverting remote connections on it logs all of the information being sent.
This mean PII is getting into the logs which is something Joshua said not to do, and something we agreed not to do.
This crept in because we originally didn't divert on servers that had real data.
Now that we do we should remove information with PII from any logging and print functions. As side note while removing that information we should switch to using logs in any place that still using print statement, its trivial.
We should also discuss what to do about the logs on both production and staging. This data is currently stored in papertrail and in a bucket in AWS. Its unclear how to empty papertrail