fix(rtdb): Support parsing non-US RTDB instance URLs #517
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.
The SDK currently only supports production RTDB URLs with the hostname
firebaseio.com
. But RTDB instances deployed in non-US regions seem to have different hostnames likefirebasedatabase.app
. This PR implements support for such URLs.The updated URL parsing scheme is as follows (in the specified order):
FIREBASE_DATABASE_EMULATOR_HOST
environment variable is set, we use it as an emulator URL. Namespace is extracted from the databaseUrl app option.FIREBASE_DATABASE_EMULATOR_HOST
, then we treat it as a production URL.We don't check production URLs for any specific hostnames. But this can be added if necessary (given RTDB hostnames are a fixed set).
Resolves #514
RELEASE NOTE: Added support for handling RTDB URLs that point to instances hosted in non-US regions.