-
Notifications
You must be signed in to change notification settings - Fork 933
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check for readyness #5009
Comments
I now added a function |
Have you tried |
I've been working on this recently. So far my approach is to use docker compose to bring up the stack (where the FB emulator suite is a dependent service) and I'm waiting for FB to be ready using
Hope it helps. As you can see, I'm polling this REST endpoint to know wether the Auth service is up and running: |
For CI we want to run the emulator suite in a docker service container (github actions). We need to able to check from the main script if the emulator is "ready". That means a couple of things:
firebase.json
to show up.firebase.json
has shown up (because the main github action thread ran "checkout") we extract the location of the functionspackage.json
and wait for it to show up.package.json
has shown up, we can finally start the emulators, as they would crash if the functionspackage.json
is not present (btw: it suffices to put in{}
to thispackage.json
so the check is pretty pointless...). Here is the script for step 1. - 3. The functionspackage.json
shows up once we have run ourbuild
step.waitFor localhost:4000
which returns too early!Is there something like
http://localhost:4000/functions/health
or so?The text was updated successfully, but these errors were encountered: