Headless Chrome support in Cloud Functions and App Engine

Re:Headless Chrome support in Cloud Functions and App Engine by djm_ on Monday August 20, 2018 @05:40AM (#17798672)

> Run a SQL query to anonymize all of PII columns for GDPR compliance as data has now left the EU.

Do you ensure the values you replace with 'make sense' in the context of the application? i.e are names turned into fake names?

If so, I would love to hear more about you handle the complexities of this. If not, it's still a wonderful pipeline that I'm putting my ideas box, thanks for sharing.

[ Parent | on HN ]

Re:Headless Chrome support in Cloud Functions and App Engine by tjbiddle on Tuesday August 21, 2018 @08:55PM (#17815288)

Nope! I probably could with the Faker library; but we don't care about that - and to do so would be a much heavier query. My query looks like this, so it runs extremely fast and isn't an issue on Lambda:

  `UPDATE Users set FirstName = 'FAKEFIRSTNAME', LastName = 'FAKELASTNAME', StreetAddress = '123 FAKE ST.', Zip = '10001', PrimaryEmail = Cast(NewId() as varchar(36)) + '@x.com', Phone = '555-555-5555')`

[ Parent | on HN ]