Firebase emulators: auth data is not exported/imported? - firebase

I use Firebase emulators with the auth emulator (very happy with this new feature!)
I signup a user using email and password -> I can see it created in the emulator UI.
I insert some data in Firestore -> it works equally well.
I export the data:
firebase emulators:export local_data
Later on, I restart the emulators with the exported data:
firebase emulators:start --import=local_data
The Firestore data is loaded correctly, but the user I created previously does not exist!
It seems that the auth emulator data is not exported or not imported.
Am I doing something wrong?
Edit: this feature has been implemented by Firebase!
With CLI version > 9.1.0 one can export and import auth data from the emulators, cool!
see this Github announcement

According to the documentation:
emulators:export export_directory
Cloud Firestore or Realtime Database emulator. Export data from a running Cloud Firestore or Realtime Database emulator instance
So the emulators:import and emulators:export commands currently only work on Cloud Firestore and Realtime Database. As Doug commented, it is a valid feature request, so thanks for filing it on the Github repo.

Related

Run firebase functions emulator on database without database emulator (towards production cloud instead)

I am having trouble running the firebase functions emulator towards a production database. I have a project which is not publicly released yet so I can run towards production with any negative effects.
My project uses only the realtime database, it does not use Firestore (so other questions on SO are not relevant) The documentation states "Cloud Firestore and Realtime Database triggers already have sufficient credentials, and do not require additional setup." so according to that, I shouldn't need any additional setup in order to point to the production database.
According to all of the documentation on Firebase, the project should run towards the real firebase database if I only start the functions emulator and do not start the database emulator. This warning seems to say so, too:
functions: The following emulators are not running, calls to these services from the Functions emulator will affect production: auth, firestore, database, hosting, pubsub
However, this is not what happens. Instead, I get the following error:
functions[onGlobalClientRequest]: function ignored because the database emulator does not exist or is not running.
I have read the firebase documentation and nothing is really mentioned other than setting credentials should not be needed (but I am setting credentials anyway using export GOOGLE_APPLICATION_CREDENTIALS="/path/to/credentials.json" before running the functions emulator.)
onGlobalClientRequest looks like this:
export const onGlobalClientRequest = functions.database
.ref( client_requests_key + "/{pushedid}")
.onCreate(
async (
snap: functions.database.DataSnapshot,
context: functions.EventContext,
) => {
///.... code here...
},
);
The locally emulated Firebase Functions will be able to write to the Prod database, but will not be able to get triggered by the production database.
Here is a SO answer from a Google employee that states the aforementioned.
Also, quoting from this other SO answer from another Google employee:
In general the rule with emulators:start is that we comprehensively emulate whatever is running. So for example if you're running the Functions and Database emulator, all writes from functions (through admin.database().... will be redirected to the Database emulator. But writes to Firestore (admin.firestore()...) will try and hit production because that emulator is not running.
Operations on a Realtime Database (RTDB) trigger the functions in the corresponding project. So the production RTDB triggers functions of your production project, and the emulated RTDB triggers emulated functions.
If you want to test functions triggered by RTDB operations locally with the emulator, you have to use the RTDB emulator as well. This is explained in the doc here.
If you only want to test HTTP callable functions, then you can use a remote RTDB.

Could I use GCP infrastructure as a code to setup Firebase Auth, Firestore, RDB, Cloud Functions?

I know that I could setup Cloud Firestore and GCP Cloud Functions with infrastructure as a code, but I'm interested that it will be shown at the Firebase Console. I also can't find any way to deploy Firebase Auth and Realtime database with IaaC.
Any Cloud Functions deployed by either the Firebase CLI or gcloud will appear in both the Firebase console and the Cloud console.
Any data populated in Firestore will also appear in both consoles.
The Cloud console has no view into Firebase Auth or Realtime Database, as those services are unique to Firebase. You will have to use the Firebase console and its tools and SDKs to work with those products.
In fact, a Firebase project is just a Cloud project with extra APIs and services enabled on top. You might be helped by reading this blog series on the relationship between Firebase and Google Cloud.
https://medium.com/google-developers/whats-the-relationship-between-firebase-and-google-cloud-57e268a7ff6f
https://medium.com/google-developers/firebase-google-cloud-whats-different-with-cloud-functions-612d9e1e89cb
https://medium.com/google-developers/firebase-google-cloud-whats-different-with-cloud-firestore-40f1fc3e6d1e
https://medium.com/google-developers/firebase-google-cloud-whats-different-with-cloud-storage-a33fad7c2b80

How To Prevent Firebase Firestore Emulator From Clearing The Database At Exit?

I'm Planning To Use Firebase - Firestore Emulators For Handling Some Huge Amount Of Data That's Coming From A Websocket.
I just need to process the data locally in realtime.
Firestore Emulator Is A great choice since it has all the features I need. But the issue is it clears the database every time the Emulator is turned off. is there any config or settings that can change this behaviour?
if it is not possible. can somebody tell me any other Approach to use firestore locally? or any other alternative to firebase that I can use locally.
With the recent updates to Firebase Emulator, you use export the data when the emulator is running and import when it starts again.
To export the data
firebase emulators:export <export-directory>
To start and import the emulator
firebase emulators:start --import <export-directory>
I've managed this starting Firebase emulator with parameters to export data on exit and import existing one:
firebase emulators:start --import=exported-dev-data --export-on-exit=exported-dev-data
This way the emulator always export the data I've generated to folder exported-dev-data, and loads it back when starting again.
Currently you need to write code to populate the database during each run of the emulator.
If you would like to see different behavior, please file an issue on GitHub.

Unable to trigger firestore changes locally

I just started doing firebase and I need to do something when a new document is created but in functions and I setup cli and started locally but the function is not triggered.
while doing firebase init I chose firestore,functions,storage
after that did firebase login and firebase serve --only functions
and the server is up but whenever I add new document the function is not getting triggered?
You should be able to do that with firebase emulators:start. This starts emulators for Cloud Functions, Cloud Firestore, Realtime Database and Firebase Hosting. If that doesn't work, please share your code and I can have a look.
The docs may be useful too: https://firebase.google.com/docs/functions/local-emulator#run_the_emulator_suite

Firebase CLI database:get request always return null

I am the owner of the firebase project from which I am trying to fetch the data, e.g., firebase database:get /orders. However, the request always returns null. I tried to set up different roles https://console.cloud.google.com/iam-admin/iam?project=[myproject] with no luck. I have only one firebase project and it is selected as I can see in firebase list. I can deploy functions and app from the Firebase CLI.
You should check that your /orders path exists in Realtime Database and not Firestore. The command firebase database:get is for interacting with Firebase Realtime Database only and not Firestore.

Resources