feat: find emulator project id from environment variable #843
+36
−2
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.
Previously, if
FIRESTORE_EMULATOR_HOST
was set and aClient
instance was created without an explicit project, it would fall-back togoogle-cloud-firestore-emulator
This change makes it check the
GCLOUD_PROJECT
variable for a project id first, which is used by the firebase functions emulator. This means the client will auto-detect the project id if not given in the emulator, just like in a live GCP environmentFixes firebase/firebase-functions-python#174
BEGIN_COMMIT_OVERRIDE
fix: find emulator project id from environment variable
END_COMMIT_OVERRIDE