Retiring the legacy environment configuration feature for Cloud Functions for Firebase (1st gen).

Database & APIs

Hello Alan,

You’re receiving this communication because we’re retiring the legacy environment configuration feature for Cloud Functions for Firebase (1st gen). To ensure seamless deployments and enhanced security, you will need to migrate your deployment to Secret Manager.

We’ve provided additional information below to guide you through this change.

What you need to know

Key changes:

Potential impact:

  • Existing Cloud Functions: Your currently deployed Cloud Functions for Firebase will continue to run without interruption.

  • New Deployments: After March 31, 2027, you will not be able to deploy updates to Cloud Functions for Firebase that rely on the legacy Cloud Runtime Configuration API.

  • Data Access: After March 31, 2027, the underlying Runtime Configuration API will be inaccessible for all Firebase users. You must export your data before this deadline to avoid potential data loss.

  • Cost: Most users will experience no change in cost. Storing non-sensitive configuration in .env files is free. Secret Manager provides a free tier of six active secret versions for sensitive data, which should cover most projects.

What you need to do

Action required:

To ensure seamless deployments and enhanced security, please take the following steps to migrate your configuration:

  1. Export your configuration: Update to the latest Firebase Command Line Interface (CLI) and run the Firebase functions:config:export command. The tool will automatically format your existing data for Secret Manager. To manually export and set a secret, run:
    $ firebase functions:config:get | firebase functions:secret:set MY_SECRET --format=json

  2. Update your code: Replace references to functions.config() in your code with defineJsonSecret (for sensitive data) or defineString (for non-sensitive data).

  3. Deploy: Run Firebase Deploy to apply these changes.

Timeline:

Please complete these steps by March 31, 2027

Impacted projects:

Your affected projects are listed below:

What have you tried so far?

Do we need to take action or FF team will? Thanks!

Did you check FlutterFlow's Documentation for this topic?
No
2
1 reply