Support caching dev seed in external storage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem

With !16700 (merged) in place, we're introducing a considerable workload for seeding the database, writing millions of records.

That costs development time as we need to wait at least more 30 minutes to seed all these records.

Time spent waiting for seeding will keep growing as we introduce more mass insertion processes.

Solution proposal

  1. Persist a dev database dump (generated through regular seeding) in an external storage (or LFS?)
  2. Create a process (weekly?) that will update this seed DB dump
  3. Create an accessible script (e.g. bin/load_seed_dump) that will download the latest seed and load to the local DB
  4. Ideally, bin/load_seed_dump should go back to the SHA where the seed was created (git checkout SHA), load the dump, go back to the upstream HEAD and rake db:migrate, as relations might have changed through migrations

Benefits

No dev downtime for seeding the database.

Edited by 🤖 GitLab Bot 🤖