Ab März 2027 muss der Google Secret Manager verwendet werden und nicht mehr firebase.config()
Siee Mail:
Hello Joerg,
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:
We’re retiring the legacy Cloud Functions for Firebase configuration feature, which relies on the Google Cloud Deployment Manager.
We’re transitioning to Secret Manager for sensitive configurations and standard environment variables for non-sensitive ones. This aligns our practices with the security standards used in Cloud Functions for Firebase (2nd gen).
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:
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
Update your code: Replace references to functions.config() in your code with defineJsonSecret (for sensitive data) or defineString (for non-sensitive data).
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:
espdata-b473e
We’re here to help
For instructions and code examples on how to migrate your environment configurations to the new standard, please consult our official Migration Guide.
If you have any questions or require assistance, please contact Google Cloud Support.
Thanks for choosing Cloud Functions for Firebase.
– The Google Cloud Team
Ab März 2027 muss der Google Secret Manager verwendet werden und nicht mehr firebase.config()
Siee Mail:
Hello Joerg,
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:
We’re retiring the legacy Cloud Functions for Firebase configuration feature, which relies on the Google Cloud Deployment Manager.
We’re transitioning to Secret Manager for sensitive configurations and standard environment variables for non-sensitive ones. This aligns our practices with the security standards used in Cloud Functions for Firebase (2nd gen).
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:
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
Update your code: Replace references to functions.config() in your code with defineJsonSecret (for sensitive data) or defineString (for non-sensitive data).
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:
espdata-b473e
We’re here to help
For instructions and code examples on how to migrate your environment configurations to the new standard, please consult our official Migration Guide.
If you have any questions or require assistance, please contact Google Cloud Support.
Thanks for choosing Cloud Functions for Firebase.
– The Google Cloud Team