Functions config deprecation warning even though I'm not using that API

[sjudd]

[REQUIRED] Environment info

firebase-tools: 14.11.1

Platform: OSX

[REQUIRED] Test case

[REQUIRED] Steps to reproduce

Every time I deploy, I see the deprecation warning for functions.config() API is deprecated.. I'm not using and have never used that API. How can I figure out what's triggering this call and be certain that either I remove it, or that it will not stop me from deploying?

 DEPRECATION NOTICE: Action required to deploy after Dec 31, 2025
  
  functions.config() API is deprecated.
  Cloud Runtime Configuration API, the Google Cloud service used to store function configuration data, will be shut down on December 31, 2025. As a result, you must migrate away from using functions.config() to continue deploying your functions after December 31, 2025.
  
  What this means for you:
  
  - The Firebase CLI commands for managing this configuration (functions:config:set, get, unset, clone, and export) are deprecated. These commands no longer work after December 31, 2025.
  - firebase deploy command will fail for functions that use the legacy functions.config() API after December 31, 2025.
  
  Existing deployments will continue to work with their current configuration.
  
  See your migration options at: https://firebase.google.com/docs/functions/config-env#migrate-to-dotenv

[REQUIRED] Expected behavior

I should not receive a deprecation warning for an API I'm not using. Or it should point me to the specific usage so I can remove it, which is especially important if it's a transitive dependency that I'm not aware of.

[REQUIRED] Actual behavior

I'm warned that I can't deploy next year due to an API I do not use.

[google-oss-bot]

This issue does not have all the information required by the template. Looks like you forgot to fill out some sections. Please update the issue with more information.

[joehan]

Hey @sjudd, its very possible that there is a false positive in this logic, but its hard to be sure without seeing your code. @taeold can probably help more if you can provide a code sample/MVR

In case it helps, here's the logic that tirggers that warning (https://github.com/firebase/firebase-tools/pull/8808/files#diff-8c0dbfe0d66a9115ed3f609c08fde3037d781eec7b8cc57d54fdf2048f11ea87R93) - it should only be showing if there is something in your Runtime Config.

[sjudd]

Unfortunately it's not super practical for me to give you the source code for a bunch of functions. Can you provide any more specific information in your warning message about where the usage is coming from? I'm not even sure where to start really.

I can say that "functions.config" does not appear anywhere in my codebase. Is there some other way that API could be used that I should look for?

[sjudd]

One more thing I tried - I ran firebase functions:config:export. My .env.local, .env.dev and .env.prod files all already eisted, but I let it create a new .env file. The file it created was empty other than a comment:

samueljudd@Samuels-MacBook-Pro-2 firebase % cat ../.env
# Exported firebase functions:config:export command on 8/1/2025# .env file contains environment variables that applies to all projects.
samueljudd@Samuels-MacBook-Pro-2 firebase % 

[gmbenedek]

The issue is absolutely the same for me.

[maganap]

@sjudd

How can I figure out what's triggering this call and be certain that either I remove it, or that it will not stop me from deploying?

Same issue. And as a prediction you did... I could not deploy today because of this.

If anyone can't deploy today because of Cloud Runtime Config failing, there's a workaround here.

[sjudd]

@sjudd

How can I figure out what's triggering this call and be certain that either I remove it, or that it will not stop me from deploying?

Same issue. And as a prediction you did... I could not deploy today because of this.

If anyone can't deploy today because of Cloud Runtime Config failing, there's a workaround here.

Thanks for the link!

[sjudd]

For what it's worth, I have two codebases, a typescript one and a python one. If I deploy with --debug --only functions:<codebase>, I see the same empty response to runtimeconfig in the logs:

[2025-08-06T18:01:16.534Z] >>> [apiv2][query] GET https://runtimeconfig.googleapis.com/v1beta1/projects/nurse-andy/configs [none]
[2025-08-06T18:01:16.716Z] <<< [apiv2][status] GET https://runtimeconfig.googleapis.com/v1beta1/projects/nurse-andy/configs 200
[2025-08-06T18:01:16.716Z] <<< [apiv2][body] GET https://runtimeconfig.googleapis.com/v1beta1/projects/nurse-andy/configs {}

I continue to get deprecation warnings.

[TheRealMikeD]

Got the same error today, under the same circumstances. I did a search for "functions.config" in my codebase, including all node_modules. The only hits were in firebase-functions (4.7.0) and firebase-functions-test (0.2.0):

5 results - 4 files

functions/node_modules/firebase-functions/lib/v1/config.js:
  42      if (process.env.K_CONFIGURATION) {
  43:         throw new Error("functions.config() is no longer available in Cloud Functions for " +
  44              "Firebase v2. Please see the latest documentation for information " +

functions/node_modules/firebase-functions-test/CHANGELOG.md:
  1: - Fixes a bug where `functions.config()` would return old config values if `process.env.CLOUD_RUNTIME_CONFIG` was changed after the first call to `functions.config()`.

functions/node_modules/firebase-functions-test/lib/main.d.ts:
  61  export declare function makeChange<T>(before: T, after: T): Change<T>;
  62: /** Mock values returned by `functions.config()`. */
  63  export declare function mockConfig(conf: {

functions/node_modules/firebase-functions-test/lib/main.js:
  121  exports.makeChange = makeChange;
  122: /** Mock values returned by `functions.config()`. */
  123  function mockConfig(conf) {

I was not even previously aware that there was a "functions.config" API. I have certainly never knowingly used it.

[NNskelly]

Same issue, and unfortunately I'm stuck using v1 functions (possible positive flag per TheRealMikeD) for auth.user.onCreate and auth.user.onDelete, neither of which have v2 equivalents. Checking the docs every few moths, the ongoing recommendation by Google is to keep using v1 for auth triggers.
If v1 functions are going to prevent new deployments after 2025, there really MUST be an alternative to v1 functionality (notwithstanding this project now needs to be forced to nodejs20 globally since v1 does not support node22), or at least an official statement of total obsolescence of anything not provided in v2.