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
Firebase functions experimental shell runtimeconfig #477
Comments
Supporting config automatically during emulation without you having to run "firebase functions:config:get > .runtimeconfig.json" is on our roadmap. Thanks for the validation! |
Any update on timeline / estimate here? Been running into this bunch lately :/ Thanks! |
I recommend editing the "shell" script in your functions/package.json to be:
That way you can just run "npm run shell` |
This still scares me because if you ever accidentally invoke firebase shell directly rather than via npm, you could use the wrong config, but it's better than nothing. From firebase/firebase-tools#477 (comment)
Closing for inactivity. |
* enables permission checking; * format
Version info
Steps to reproduce
On a few occasions, I've ran
firebase functions:config:get > .runtimeconfig.json
outside of my functions folder.I'm swapping between a few different projects, and forgetting to cd into /functions
Then getting confused why my config is wrong or doesn't exist after local deploying in shell
Expected behavior
It's probably more of a feature request than a bug:
If firebase experimental:functions:shell could warn about .runtimeconfig.json if it sees there's one on the wrong folder level, that would be helpful
Actual behavior
firebase experimental:functions:shell essentially does exactly what it should be doing.
The text was updated successfully, but these errors were encountered: