pangea-extensions-firebase VS extensions

The Pangea Extensions you will install in the following few sections of this tutorial are actually pre-packaged Cloud Functions provided by Pangea that you can deploy and authorize to run in your Firebase environment. All the Pangea Extensions are open source and available for you to reference, modify, and improve. You can visit our Github Repository to view or download the code. To learn how to quickly leverage the power of Pangea's security services without needing to write or debug code proceed to the next section.

Are you trying to avoid copying the file from the /tmp directory after it is processed? As part of my work at Pangea.cloud, I developed as Firebase Extension, https://github.com/pangeacyber/pangea-extensions-firebase/tree/main/storage-file-intel , that scans files for malicious behavior after a user uploads a file. If the file is deemed dangerous, it gzips it and moves the .zip file to a /malicious folder in Cloud Storage. This all works automatically because the processing function is set as a trigger to cloud storage events. Are you using triggers?

Let me know if you try it out. We just updated it to post events when a malicious file is detected. This is a huge improvement because 1) developers can add custom logic to respond accordingly 2) If you also install the Secure Audit Logging extension the event is automatically logged on a tamper proof blockchain. The details on the audit logging are available here: https://pangea.cloud/docs/tutorials/firebase/audit/

In this tutorial, learn how to install and utilize a combination of Pangea provided Firebase Extensions. Firebase Extensions are an easy way to add Pangea services to your Firebase app without the need to write or debug code on your own. Extensions are pre-packaged solutions designed to save development time and quickly deploy Pangea functionality into your applications hosted on Firebase. You provide the configuration parameters, such as authentication tokens, for each extension at install time. All Pangea-provided extensions are open-sourced and built on Firebase and Google Cloud products you already know. Deployment and configuration of each extension are performed in the Firebase console or the Firebase CLI, and once deployed, they require no maintenance.

If you want to try the Extension, check out this tutorial. Accepting user uploads is the use case we developed the Extension. Depending on your use case, and if you want to share your app's processing capabilities with other Firebase developers, you might want to consider building it into a Firebasse Extensions

Firebase Extensions: Pre-packaged development solutions 🔗Link

According to this discussion the Node version is set by the Firebase team, which is quite sad. Please let me know if I'm wrong, but it seems like it's not under our control.

Also see the delete user extension for an example: https://github.com/firebase/extensions/tree/master/delete-user-data

So this provides an obvious question, how do I import previously existing data? We have an import script for that!

Hi all, I need to add some data into BQ, the data was in my Firebase before I installed the "Stream Collections to BigQuery" extension. So now I need to load it manually. I'm trying to use fs-bq-import-collection, but my issue is that the collection I want to import is a subcollection e.g. /collection/{document}/sub_collection. I've read the documentation https://github.com/firebase/extensions/blob/master/firestore-bigquery-export/guides/IMPORT_EXISTING_DOCUMENTS.md and there they say that I need to use a collectionGroup query. But I really have no idea how to do that, I've spent several hours checking the net but I cannot find any place that explains it in a easy to understand way.

Method 3: - Distributed Counters - Whenever you deal with any real scaling, you need something like the sharding to accurately keep track of document counts. If you have more than 1 page view a sec, or more than one person clicks like a post a second, the server will slow down, and potentially be inaccurate. You can fix this with sharding. Here is the Firebase Extension and the Source Code. The code is really well written, but it should never have had to be written! Indexes, indexes, indexes!