Node.js – Set Firebase local emulator cloud function environment config values

firebasegoogle-cloud-functionsnode.js

When you update cloud function environment variables, the config values are not accessible when using the local node.js emulator.

On a project with no environment config variables:

Set a new value firebase functions:config:set x=true
Get the config variables firebase functions:config:get (shows the new value)
Deploy the functions firebase deploy --only functions
Run the local emulator and log out the functions.config{}
Output: {} (empty object)

There is no mention in the environment config docs but I am assuming it is possible to use the same environment config locally (or a local alternative)?

Best Answer

The answer was in the local emulator documentation.

Note: You can retrieve your production custom configuration variables when emulating functions. However, be cautious when using production config values in local testing of API calls, emails, etc.

To use config variables, run the following command in the functions directory before running firebase serve.

MacOS

firebase functions:config:get > .runtimeconfig.json

Windows

firebase functions:config:get | ac .runtimeconfig.json

Related Solutions

Javascript – Enabling CORS in Cloud Functions for Firebase

There are two sample functions provided by the Firebase team that demonstrate the use of CORS:

The second sample uses a different way of working with cors than you're currently using.

Consider importing like this, as shown in the samples:

const cors = require('cors')({origin: true});

And the general form of your function will be like this:

exports.fn = functions.https.onRequest((req, res) => {
    cors(req, res, () => {
        // your function body here - use the provided req and res from cors
    })
});

Node.js – Cloud Functions for Firebase – Billing account not configured

The "Billing account not configured" warning message is automatically logged by Google Cloud Functions when no billing account is configured. It doesn't mean that your code isn't working, but it merely there as a reminder just in case you have a problem.

The restriction is about outbound access - e.g. can your Function request resources from the general internet. Its absolutely fine to use a function to respond to a webhook, or to access Google-internal services such a the Realtime Database.

If you wanted to call a third party web service (for example) you'd need to enable billing.

For the other quotas, take a look at: https://firebase.google.com/pricing/ - as you can see there are limits to the number of invocations (125,000 at time of writing) and CPU and memory (40k cpu-seconds and 40k GB-seconds) in the free tier.

Best Answer

Related Solutions

Javascript – Enabling CORS in Cloud Functions for Firebase

Node.js – Cloud Functions for Firebase – Billing account not configured

Related Topic