Anonymize db

[gadogado]

Overview

This PR adds postgres comments to all columns that should be anonymized when the database is dumped via pg_dump. The fake_pipe library will reflect on all pg comments when the database is dumped and will anonymize the data with Faker for the respective target type, e.g, sentence, word, bcrypt_password, md5, etc. (supported conversions)

Changes

There's a new migration that adds all of the comments. This needs to be run on the database before its dumped and anonymized. After this is complete you can use a new rake task to dump, restore, and even setup an anon user for testing.

How to test

1. Load your database ( or use the existing one ) with whatever db you want to anonymize.
2. Run the migrations
3. Dump and and anonymize the output file: rake db:anon_dump ( Takes ~ 8 mins on my local )
4. Restore with the anon dump file that was created: rake db:anon_restore
5. Setup one of the users for dev testing: rake db:setup_anon_user
6. Do a manual audit and make sure everything is anonymized. I usually use something like postico for this

Possible issues

1. The dump process should ignore acls and owners. If there's any issues you can create a missing user with the usual: CREATE USER postgres SUPERUSER;

TODOS

• fork fake_pipe to add a number mutator

[codeclimate]

Code Climate has analyzed commit d40ac72 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (80% is the threshold).

This pull request will bring the total coverage in the repository to 87.4% (0.0% change).

View more on Code Climate.