Firebase - Migrate your Cloud Run functions (1st generation) to Artifact Registry

Integrations

Hey!

Anyone also got this email?

We are writing to remind you that Google Container Registry (GCR) has been discontinued and is scheduled for shutdown after March 18, 2025. We recommend that you change the default container registry settings for your 1st generation functions to use Artifact Registry (AR) as soon as possible.

For functionality and pricing differences between GCR and AR, refer to the transition document.

What you need to know

Cloud Run functions (1st generation) provides support for two container registry types:

  • Google Container Registry

  • Artifact Registry

Cloud Run functions (formerly known as Google Cloud Functions 2nd generation) only supports Artifact Registry.

Please review the dates below:

  • 1st generation functions created on or before January 15, 2024 use Container Registry as the default container registry.

  • Starting February 18, 2025, deployments of 1st generation functions will transition to using Artifact Registry regardless of the previous selection.

We have identified that you have at least one 1st generation function that uses Container Registry as the default container registry.

Your affected projects can be found in the attachment below:

What you need to do

Follow these steps to identify 1st generation functions that are still using Container Registry:

  1. Identify which 1st generation functions are still using Container Registry

  2. Migrate your projects from Container Registry to Artifact Registry with the automatic migration tool.

No action is required from you if:

  • Your 1st generation functions are using Artifact Registry as the default container registry.

  • Your 1st generation function is a Cloud Function for Firebase created with Firebase CLI version 11.2.0 (release June 30, 2022) or higher.

  • It is a Cloud Run function (formerly known as a Google Cloud Function 2nd generation).

I'm wondering if there's any upcoming solution from FF to migrate cloud functions / private APIs directly to AR? Or should we manually do this in Google Cloud?

I have attached a screenshot of the package.json file in my cloud functions in FF.

--edit:

I have found this part in the Google Cloud documentation:

So I double checked the functions details in my project & it seem to be already set to "artifact registry":

"dockerRegistry": "ARTIFACT_REGISTRY", "automaticUpdatePolicy": { }

So I'm thinking probably there's nothing to do from my side but still would like to know 100% if this is the case to avoid any disruptions.

What have you tried so far?

I have searched in the community but couldn't find an answer

Did you check FlutterFlow's Documentation for this topic?
Yes
7
6 replies