fix(firestore-bigquery-export): kit/extension parity - DATABASE_REGION offers europe-north2, northamerica-south1 and asia-southeast3, which can't deploy #3291

firestore-bigquery-export kit/extension parity. Three DATABASE_REGION choices can never deploy.

Difference

The kit deploys its functions to the region set in DATABASE_REGION. It offers europe-north2, northamerica-south1 and asia-southeast3, but Cloud Functions has no location in any of them: gcloud functions regions list does not include them, while gcloud run regions list does. The extension offers the first two, but it only uses DATABASE_REGION for the trigger region and deploys the function to LOCATION. This is the same problem as #3268 in storage-resize-images.

Reproduced

With DATABASE_REGION=europe-north2 in .env, firebase deploy --only functions (firebase-tools 15.32.0, with the kit's engines.node changed from >=22 to 22, which this CLI version requires) fails before any function is created:

Error: Request to https://cloudfunctions.googleapis.com/v2/projects/<project>/locations/europe-north2/functions:generateUploadUrl had HTTP Error: 403, Location europe-north2 is not found or access is unauthorized.

northamerica-south1 and asia-southeast3 fail with the same error. With europe-west1, the deploy gets past this step. The project's Firestore database was in us-central1, which does not affect the result, since the deploy fails before any trigger is set up.

Code

• Kit: config.ts#L158, #L172, #L181.

Resolution

Remove the three options and reject them when set in .env, as #3283 does for storage-resize-images. Mapping them to a nearby region may also work if a Firestore trigger can reach a function in another region, as the extension's does, but that has not been tested for the kit.