11 results found
-
CLI deploy and link blocking functions
Function Deployment & Validation Flow:
When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:
.
Detect Blocking Function Patterns
Check if the deployed function's name matches known blocking trigger conventions..
Assignment Validation
Verify whether the detected function is registered as a blocking trigger in the system configuration..
Interactive Guidance
If unassigned, display CLI prompt:
"Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. To configure this function visit: <CONSOLE URL>".
Key Function Patterns:beforeCreate | beforeSignin | afterSignout | customBeforeHookWhy This Matters:
…
1 vote -
CLI deploy and link blocking functions
Function Deployment & Validation Flow:
When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:Detect Blocking Function Patterns
Check if the deployed function's name matches known blocking trigger conventions.Assignment Validation
Verify whether the detected function is registered as a blocking trigger in the system configuration.Interactive Guidance
If unassigned, display CLI prompt:
"Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. Would you like to configure this function now? (y/N)"Key Function Patterns:
```
beforeCreate | beforeSignin | afterSignout | customBeforeHook(Additional supported hooks)
…Why1 vote -
Support a repl/shell in firebase CLI
Some operations can only be preformed through the firebase-admin SDK, or sometimes you just want to run/test some Firestore query.
The Firebase CLI can provide a "shell" command that opens a Node.js REPL with the firebase-admin SDK preconfigured and global variables such as "db", "auth" that you can then use to interact with Firebase.
This was so much needed that I implemented this by myself in our project as a custom package.json scripts.
2 votes -
Support skipping deploy targets that are configured empty
Sometimes you have deploy target that you want to not deploy in some projects.
Currently if a deploy target is not configured or empty, the CLI will error.
It would be nice if it just skipped deploying that configuration if the deploy target is explicitly configured empty.
This is also useful to allow varying configuration in different projects, as you can deploy different target configurations depending on the selected project this way.
2 votes -
Remove git from functions folder
Using firebase init will create a git submodule in the functions folder, which is a giant hassle to remove. I just want init git in the root project.
1 vote -
Firebase CLI (Python version) should provide debugging information
Add better debugging information into Firebase CLI (Python) version. The CLI frequently throws the following error but does not provide any further information, even in debug mode.
Failed to call quitquitquit. This often means the server failed to start request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081 {"message":"request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}
or
Error: User code failed to load. Cannot determine backend specification
Details of the error can however be found in the GCP Console and Cloud Build. The same error messages should appear in the CLI as the Console is not a scalable way to maintain/deploy…
2 votes -
Support monorepo
Firebase functions does not support monorepo structures (NPM monorepo, NX, Turborepo) during deployment.
Firebase uses custom archive logic for functions packaging (https://github.com/firebase/firebase-tools/blob/127ca3fbf7549d6c0cdf12e89e4465de9dd2b7c9/src/deploy/functions/prepareFunctionsUpload.ts), which does not support internal packages deployment out of the box.
Github discussion: https://github.com/firebase/firebase-tools/issues/653
23 votes -
deploy specific extension
Allow deployment from CLI of specific extensions, to avoid uploading and updating all extensions unnecessarily.
i.e. firebase deploy --only extensions:<name of extension>
Just like we can with functions.
3 votes -
Add TTL dynamically
Similar to the way we can define an index in firestore with
firestore.indexes.json. I'm proposing afirestore.ttl.jsonwhere the TTL properties would be deployed uponfirebase deploy, instead of having to go in the console UI or alternative methods.Those configuration files are useful when switching environment as this minimize the configuration required when going from dev, to staging, to prod. Centralizing those in one place makes it easier.
3 votes -
firebase framework sveltekit environment (vite mode mode)
in a svelte-kit app if you have multiple environments (staging, production) you can specify multiple .env files.
Unfortunately, there is no way to tell Firebase which one to use so it always deploys using production. and always uses development in the emulator
4 votes -
Set GCP resource location locally or have it be faked when using Firebase without a project.
I'm currently learning Firebase and want to have a sandbox with the emulators without creating a project on the website every time I want to make another. Currently Firebase Storage does not work without setting a GCP resource location and the only way to set it is via the web console. If there was a way to set it locally via the CLI or a config file that would make it a lot easier to experiment with Firebase.
2 votes
- Don't see your idea?