feat: Add global dataDir for emulator persistence #8782
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.
Implements a global
emulators.dataDir
setting infirebase.json
to allow users to easily persist and re-load emulator data across sessions.Key changes:
emulators.dataDir
tofirebase.json
schema.firebase init emulators
to prompt fordataDir
configuration.--ephemeral
flag toemulators:start
andemulators:exec
to ignoredataDir
for a single run.dataDir
on startup if it exists and contains valid export metadata.dataDir
on clean shutdown ifdataDir
is configured (and not overridden by--export-on-exit
flag).emulators.dataconnect.dataDir
, preferring the globalemulators.dataDir
with warnings.Description
Scenarios Tested
Sample Commands