Currently we're using rush seed-firestore:<eisbuk|igorice> which are actually two different (but very similar commands) by running node backup-restore (backup-restore being cli.js). The problem with that approach is: we can't pass any arguments, hence the two different commands. I would prefer to be able to run rush seed-firestore -o <igorice|eisbuk> which would then be a single command. Additionally, as mentioned in #865 it would be nice to split the backing up and restoring (seeding) into two different commands and, ideally, I would like to be able to pass some arguments to both (so that we don't have to hard-code each and every variant of each command.
In order for commands to be able to receive arguments, it would make more sense to run them as js scripts, rather than bash commands, therefore, it would be nice to be able to use the backup-restore functionality, but write a wrapper around it (hence the suggestion for the lib side of the package).
Tasks
[ ] split the functionality (as a lib) and the cli part of the backup restore package
[ ] create custom script wrappers for pulling the backup from production and seeding the local db (both should be able to accept arguments) - these can be stored in common/scripts/...
[ ] script for pulling the backup should accept one argument -o or --organization and call to the backup-restore script under the hood
[ ] script for seeding the db should check the <root>/firestore-backup for data for a given organization and use the data found there
[ ] if no backup if found in <root>/firestore-backup, it should prompt the caller if they want to pull the latest data from production
Currently we're using
rush seed-firestore:<eisbuk|igorice>which are actually two different (but very similar commands) by runningnode backup-restore(backup-restorebeingcli.js). The problem with that approach is: we can't pass any arguments, hence the two different commands. I would prefer to be able to runrush seed-firestore -o <igorice|eisbuk>which would then be a single command. Additionally, as mentioned in #865 it would be nice to split the backing up and restoring (seeding) into two different commands and, ideally, I would like to be able to pass some arguments to both (so that we don't have to hard-code each and every variant of each command.In order for commands to be able to receive arguments, it would make more sense to run them as js scripts, rather than bash commands, therefore, it would be nice to be able to use the
backup-restorefunctionality, but write a wrapper around it (hence the suggestion for the lib side of the package).Tasks
common/scripts/...-oor--organizationand call to the backup-restore script under the hood<root>/firestore-backupfor data for a given organization and use the data found there<root>/firestore-backup, it should prompt the caller if they want to pull the latest data from production