30 results found
-
Deploy Private HTTP Firebase Functions without "Allow unauthenticated"
By default HTTP Firebase Functions are made public. In Google Console they are marked as "Allow unauthenticated" because they will allow all callers, without checking authentication.
I would like an option to deploy them privately.
Example:
const privateFunction = onRequest(
{
allowUnauthenticated: false,
},
(req, res) => {
res.status(200).send(req.body);
},
);2 votes -
Auth onUpdate trigger for v1 and v2 functions
In the same way, we have onCreate and onDelete, it will be very helpful to have an onUpdate option. For example, so we can react to an email address change.
3 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.
0 votes -
Cretoin
Checking app
0 votes -
Fee/Pricing
Functions is behind paywall, (it is still free for some limit in Blaze plan), but IF i upgrade to Blaze, then Cloud Storage, Hosting etc starts to charge right away, even in free plan they have free limits but once switched to Blaze it starts to charge. So to get free Functions, i have to pay cloud storage and hosting and more.
For any playground project that is not gonna hit market or earn money, how i am supposed to try/learn functions? This forces me to move away from platform
3 votes -
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.
4 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 account3 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.2 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 -
next.js dockerfile
I am deploying using the Firebase CLI with Next.js. I find it incredibly effective and I am very grateful for it, however, I've encountered a bit of a problem.
When running code with SSR that requires a certain package, an error occurs and I'm unable to proceed.
Is it possible to use a Dockerfile or a Docker container image that I've prepared myself?
Thank you very much for your assistance.
1 vote -
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.
1 vote -
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?
4 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?
4 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.)…4 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.
1 vote -
Create a context.auth (1st Gen) equivalent for 2nd Gen cloud function
1st gen cloud functions can access auth info via context.auth as described here: https://firebase.google.com/docs/database/extend-with-functions?gen=1st#accessing_user_authentication_information
But 2nd gen cloud functions is yet to have the same function.
19 votes -
Support TypeScript in Cloud Functions
It's a pain to have to configure a process to watch and transpile TypeScript files to use in the emulator. Firebase CLI should have built-in support for it both in the emulator (with automatic watching, or on-the-fly transpilation as I showed here https://github.com/firebase/firebase-tools/issues/5633#issuecomment-1622585432) and when deploying.
13 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.2 votes -
Support Go in Cloud Functions
Go is much more efficient than Python or Js and should be the obvious choice for backend where performance is crucial
20 votes -
Support for WebAssembly in Cloud Functions
Many languages requested in other posts—Swift, Rust, Kotlin, etc.—can be implemented all at once by adding WebAssembly (WASM) and WebAssembly System Interface (WASI) to the list of Cloud Functions’s supported runtimes (and—importantly—supplying high-quality documentation).
2 votes
- Don't see your idea?