Inject FIREBASE_CONFIG environment variable for scripts executed via emulators:exec command.
#5544
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As discussed in #5536 (comment), we learned that old versions of Firebase Functions SDK always made
process.env.FIREBASE_CONFIGavailable to the underlying script that imported the Firebase Functions SDK.While making
process.env.FIREBASE_CONFIGavailable wasn't intentional, we'll consider this a case of Hyrum's Law and will try our best to fix the regression by makingprocess.env.FIREBASE_CONFIGenvironment variable available if not set in the parent process.Fixes #5536