willhlaw

Results 8 issues of willhlaw

A lot of people will also be looking at cloning the entire firebase project over to another including the auth users. Copy the answer given here, https://github.com/willhlaw/node-firestore-backup-restore/issues/26#issuecomment-376146443, into the readme.

good first issue

Motivation from https://github.com/willhlaw/node-firestore-backup-restore/issues/3#issuecomment-359745241. - [ ] Clarify operations to retrieve and backup to disk (backup), retrieve and restore to another firestore (clone), and push from backup to another firestore (restore)....

good first issue

When cloning data from from Firestore in `--accountCredentials` to Firestore specified in `--accountRestoreCredentials`, `--backupPath` is still needed or you get an error. The backup path should not be required. -...

good first issue

To prevent destroying existing data fields and to support more of a schema migration from dev to staging, add a merge feature when restoring documents from either disk or another...

enhancement
good first issue

When migrating data or backing up and restoring data, we want to completely replace the database when restoring the data. So there should be an option to clear a firestore...

enhancement
help wanted

Right now, this tool requires a service account credentials.json file to be specified to be able to access Google Firestore rules API. I think we should update it to allow...

enhancement
help wanted

I'm not sure if I've seen if Grapnel currently has conflict resolution for the same 3rd party repo but specifying different versions. Nate Finch summarizes the issues but others chime...

Great effort here. I see that you have / are planning some versioning capabilities. Perhaps, grapnel should extend the version range concept to accommodate semantic versioning based on semver. Spec...