Jacob Cable

Closing as stale, feel free to reopen if the issue persists and you can provide some more information as requested.

https://github.com/firebase/extensions/pull/2258 - change tracker https://github.com/firebase/extensions/pull/2262 - extension

Closing this as stale, feel free to reopen if the issue persists.

Hi, thanks for raising this, it's been received. We will provide updates when available.

Reproduced this [here](https://github.com/invertase/cloud-team-mre/tree/firebase-tools-8633/firebase/firebase-tools/8633) [Seems like it's the lines here](https://github.com/firebase/firebase-tools/blob/6ec69e9cf0685c439e395e4cd96388f5dc06d28c/src/deploy/functions/runtimes/node/parseTriggers.ts#L363-L366)

I think there might be a workaround, after deploying you could run: ```bash gcloud run services update uploadData \ --project=YOUR_PROJECT_ID \ --region=europe-west1 \ --network=default \ --subnet=default \ --vpc-egress=private-ranges-only ``` Can...

I think the OP's issue is misconfiguration of the extension, as @pr-Mais mentions. @KristofSochan are you also using the script cross-project, or from firestore to bigquery on the same GCP...

Hey! Extensions don't currently support v2, so we should explicitly target them, you're right. I will investigate this and get back to you. Thanks for bringing this to my attention!

I'm not sure yet whether we will need to update the code, as extensions explicitly target functions `v1` via the extension.yaml. See https://github.com/firebase/extensions/blob/next/firestore-bigquery-export/extension.yaml#L77 for example. I have still raised this...

Hi! You'll need to import from `'firebase-functions/v1' going forward I believe, the thread that @davie-robertson linked contains more information (thanks @davie-robertson!) I will raise with the team to ensure this...