create production database dumps to make local testing easier

[bhearsum]

Testing certain types of changes to ship it (product details generation, ui changes) can be difficult without proper data in the Ship It database. Even if you create some data in the database, it's difficult to ensure you have all of the different types of data you need to robustly test.

The solution we've used for this elsewhere is to create nightly database dumps of the production database, and import them at first run for local dev

In Balrog, the database is large enough, and contains some permission/ACL informations, that we need to selectively dump it. Ship It's database is small enough and contains no sensitive data, so we should be able to dump the entire database, which simplifies things.

[gabrielBusta]

Reminds me of #1396

[bhearsum]

Reminds me of #1396

Indeed! We could easily fix that once we have database dumps.

[gabrielBusta]

SRE wired up Nightly dumps. Can we call this closed? Sounds like #1396 is about getting the dumps in the local dev env

[bhearsum]

SRE wired up Nightly dumps. Can we call this closed? Sounds like #1396 is about getting the dumps in the local dev env

Sounds good to me - thank you!