62 results found
-
Add support using custom SA for 2nd gen cloud functions deployment
Currently using 2nd gen cloud functions requires having the default Compute Engine Service Account and there is no way to use custom service account.
Not all projects have the service account or have any means to re-create the default SA if it has been deleted at some point and using default service accounts is anyway something that is not recommended by Google. So currently not all can move to using 2nd gen cloud functions unless support for using custom SA is added.
7 votes -
Increase request size over 32Mb
Right now, a Firebase function can only accept a request payload size up to 32Mb.
Using it as webhook for some external APIs, we would need to have no limits or at least 100Mb limit2 votes -
In Firebase auth using phone auth in flutter, please add a feature for creating a user with a custom uid, probably via the admin sdk
In this code await admin.auth().createUser({
email: email,
displayName: name,
uid: uid,
emailVerified: false,
password: password,
disabled: false,
});, if email and password are created, please create the user via that login method and if only phone is provided and no email, then let the user be created via phone auth. So that later on, when they try to sign in via phone auth, the system doesn't create a whole new user with a new uid but just lets the user sign into that account7 votes -
Better support for Cloud Tasks, e.g. queues
It is currently already possible to create google cloud tasks. However, this could be better integrated by creating an abstraction for queues, for example, which can also be monitored and controlled via the admin console and firebase emulator.
28 votes -
Edge Runtime for functions
Bring in Edge Runtime for functions to perform high performance tasks in the edge cloud for faster responses.
20 votes -
Make the functions npm dependencies cache list public
An article and youtube video explains how to optimize cold boots by updating dependencies to 'commonly used versions' as this will increase the chance that the dependencies can already be found in the 'dependencies cache'.
https://medium.com/@duhroach/improving-cloud-function-cold-start-time-2eb6f5700f6
This is quite vague and a bit hard to reason about. Would it be possible to see a list of package names and version info for all packages in the dependencies cache?
8 votes -
Cretoin
Checking app
2 votes -
Unit tests for Python Firebase Functions
There should be unit testing for python functions like we have unit testing for typescript here: https://firebase.google.com/docs/functions/unit-testing.
5 votes -
Support Jvm languages (Java/Kotlin) in Cloud Functions
Jvm languages are not supported in Cloud Functions today, so developers need to use more than one language in their code base.
17 votes -
Add API to make it easy to build rate limiting in HTTPS functions
It would be awesome with some kind of helper built on memcache to allow rate limiting on user defined parameters.
E.g. if I build a webservice that can access an 'account' concept that I have modelled with some kind of access token I have modelled, then it would be nice to add rate limiting rules for either the specific access token or the entire account.
14 votes -
Streaming
To implement userfriendly generative AI applications it is import to stream data produced by LLMs back to the users browser. Firebase currently buffers all content and only returns when data is complete. Is the firebase team planning to implement this?
5 votes -
Need support for linked list
We need to be able to insert a new document, update an existing document or delete a document in an ordered list of about 1000 documents. We are doing this using a linked list. Firebase does not offer linked list functionality.
1 vote -
13 votes
-
14 votes
-
Ability to split Python Functions into multiple files (=enable local imports)
Right now it is only possible to write functions in
main.py, which very quickly gets overwhelmingly large. It would be good to be able to organize code into multiple files.3 votes -
Execution ID in logs generated by Firebase Functions v2
Logs generated by Firebase Functions v1 have the property
labels.execution_idthat can be used to correlate logs that pertain to the same execution. However, that property doesn't exist in logs generated by Firebase Functions v2. It's very important for debugging.6 votes -
Real-time updates for Cloud functions
With Firebase, you can have real time listeners on Firestore documents, which allow to have your UI in sync with your data.
But when you ship logic in an app, you lose control over it.
If you want to be able to update that logic after shipping, you place it in the backend (Cloud Functions), but then you lose real time updates.
It would be amazing to have functions that can fire real-time events based on Firestore updates.So the flow would be:
- There is an update in a Firestore document (or potentially other triggers like pub/sub, analitycs, etc.)…5 votes -
Add an option to host cloud function free of cost
We all knoow cloud functions are not free now. But it would be great if you kindly allow upto 3 cloud functions without all the expensive apis like cloud vision etc.
8 votes -
Green/Blue deployment pattern
Allow for deployments to be either a green or blue deployment to be able to have multiple instances of the same functions deployed within a single Firebase project.
This would help cover the gap of time between releases of client apps and Cloud Functions, which if not handled correctly cause production issues.
2 votes -
Supports Cloud SQL connection with Firebase Functions V2 natively as it was with V1
Migrating a Firebase Functions project from V1 to V2 using Cloud SQL is not feasible. It appears that Cloud SQL connections are not yet supported in V2. Cloud SQL connection works automatically and required no actions in V1. It would be beneficial if connecting to a Cloud SQL instance using V2 could be made as simple as it was before.
4 votes
- Don't see your idea?