Firestore clone support #9262
Open
Firestore clone support #9262
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rwhogg
force-pushed
the
rh-firestore-clone
branch
3 times, most recently
from
224e9f8 to
9bb892b
Compare
joehan
reviewed
Oct 7, 2025
| "block any incoming third-party traffic.", | ||
| ); | ||
| logger.info(); | ||
| logger.info(`You can monitor the progress of this clone by executing this command:`); |
There was a problem hiding this comment.
How long is this operation usually? Would it make more sense to just poll on the operation here until it is done?
There was a problem hiding this comment.
Anywhere from hours to more than a day (varies with database size). Polling might be worth doing on, say, index builds, but for clone I definitely think it's best not to.
rwhogg
force-pushed
the
rh-firestore-clone
branch
from
9bb892b to
7acd3bc
Compare
rwhogg
force-pushed
the
rh-firestore-clone
branch
from
7acd3bc to
983e3e7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add support for Firestore Database Clone
Scenarios Tested
Sample Commands
firebase firestore:databases:clone projects/myproject/databases/original-db projects/myproject/databases/clone(chooses most recent available snapshot)firebase firestore:databases:clone projects/myproject/databases/original-db projects/myproject/databases/clone2 --snapshot-time 2025-10-06T10:00:00Z(uses selected snapshot time)firebase firestore:databases:clone projects/myproject/databases/original-db projects/myproject/databases/db-with-same-encryption --snapshot-time 2025-10-06T10:00:00Z --encryption-type USE_SOURCE_ENCRYPTIONfirebase firestore:databases:clone projects/myproject/databases/original-db projects/myproject/databases/db-with-kms-encryption --snapshot-time 2025-10-06T10:00:00Z --encryption-type CUSTOMER_MANAGED_ENCRYPTION --kms-key-name projects/myproject/locations/us-central1/keyRings/testkeyring/cryptoKeys/k1firebase firestore:databases:clone projects/myproject/databases/original-db projects/myproject/databases/db-with-google-managed-encryption --snapshot-time 2025-10-06T10:00:00Z --encryption-type GOOGLE_DEFAULT_ENCRYPTION