-
Notifications
You must be signed in to change notification settings - Fork 218
Use domain in context to override RTDB domain
#683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
spec/providers/database.spec.ts
Outdated
| resource: { | ||
| name: 'projects/_/instances/other-subdomain/refs/foo' | ||
| }, | ||
| domain: 'firebaseio-staging.com' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying with the multi-region path. However, it didn't work due to a bug in the admin SDK.
I will fix that separately. For now, this will unblock testing in staging at least.
|
@laurenzlong The JS SDK right now has a bug parsing the multi-region domain, but it has no problem understanding the staging domain. /cc @sarajmunjal |
|
Move to private repos. |
See go/rtdb-multi-region-function-sdk
Multi-region realtime database will be served under different domains. In order to make sure the
DataSnapshotreturned by the function handler can connect to the appropriate RTDB, the backend will providedomainfield in the pubsub payload.