🐛 [firestore-bigquery-export] Explicitly target the firebase functions API about extensions HOT 7 CLOSED

That email, unfortunately, does not cover Firebase Extensions. This it will not affect Firebase Extensions as the change affects function deploy operations via the CLI. The Firebase Extensions deployment is done via the extensions backend (not using the CLI) so as @cabljac mentioned the functions versions defined in the extensions.yaml have full/explicit control.

from extensions.

We are also using the firebase/firestore-bigquery-export extension, and so far the extension has not been updated to Cloud Functions v2, nor has the import of the source code from firebase-functions to firebase-functions/v1 been updated. We would like to know how we can continue to use the extension after September 1st. Thank you in advance.

from extensions.

@cabljac Sorry for mentioning you directly. Can we at least get a comment on this?

from extensions.

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!

from extensions.

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 with the extensions team. If it is needed then I will put out new releases next week.

Thanks again for tagging me though, this was definitely worth us getting on top of!

from extensions.

@cabljac Thank you very much!

from extensions.

@pavelgj Thanks for the heads up. That's good news for me :)

from extensions.