-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Remove protocol from DATA_CONNECT_EMULATOR_HOST. #8396
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
The protocol should never be set according to go/emulator-suite-admin-sdk and setting it breaks the Node.js Admin SDK. Symptoms include error messages like `getaddrinfo ENOTFOUND http` because it's trying to resolve the word `http` via DNS. I have not tested whether the client SDKs tolerates it but let's just settle on the correct behavior.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #8396 +/- ##
==========================================
+ Coverage 51.08% 51.20% +0.12%
==========================================
Files 425 425
Lines 30374 30390 +16
Branches 6223 6227 +4
==========================================
+ Hits 15516 15562 +46
+ Misses 13471 13439 -32
- Partials 1387 1389 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
joehan
left a comment
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.
Thank you for adding the detailed comments too!
This unbreaks the Node.js Admin SDK who doesn't expect a protocol. The other env vars are unchanged for now but comments were added to clarify their use cases.
Description
The protocol should never be set according to go/emulator-suite-admin-sdk and setting it breaks the Node.js Admin SDK.
Symptoms include error messages like
getaddrinfo ENOTFOUND httpbecause it's trying to resolve the wordhttpvia DNS.The other environment variable
FIREBASE_DATA_CONNECT_EMULATOR_HOSTis consumed by the JS SDK, which requires a protocol right now. We've decided not to remove the protocol for now to avoid breaking the JS SDK (e.g. when used within the Functions emulator where this env var is automatically set).Scenarios Tested
Not tested
Sample Commands
N/A