fix(firestore-send-email): kit/extension parity – kit cannot deploy for databases in northamerica-south1 or europe-north2

Open Beginner friendly
#3,296 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 8 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
firebase, typescript
Domain
backend, cloud

Research direction

Start with kits/firestore-send-email/src/region.ts and compare its region handling with the existing nam5/eur3 mappings; check kits/firestore-send-email/src/config.ts for how DATABASE_REGION is used. Update the README wording at the cited section to match the behavior. Done means both unsupported regions deploy through a supported Cloud Functions location while the Firestore trigger remains in the database region.

Written by the indexing model from the issue text.

Description

kits parity type: bug

firestore-send-email kit/extension parity. Priority: medium. The kit can't be deployed for databases in northamerica-south1 or europe-north2.

Difference
  • Extension: the function runs in the extension's location (us-central1 by default). Only the Eventarc trigger uses DATABASE_REGION, so both regions in its option list work.
  • Kit: the function itself is placed in DATABASE_REGION. Only the multi-regions are remapped; regional values are used as-is. Cloud Functions (2nd gen) isn't available in northamerica-south1 or europe-north2, so the deploy fails. Both regions are still offered in the kit's DATABASE_REGION list, and there is no workaround: a blank value puts the function in us-central1, but no longer next to the database.
Reproduced
  • The Cloud Functions v2 locations list for the test project (40 entries) includes neither region.
  • A kit instance deployed with DATABASE_REGION=europe-north2 fails: generateUploadUrl had HTTP Error: 403, Location europe-north2 is not found or access is unauthorized.
Code
Resolution

Map these two locations to the nearest region that offers Cloud Functions, as is already done for nam5/eur3. The Firestore trigger still fires in the database's own region. Also correct the README's "used as-is" wording.

Dominant language
TypeScript
Stars
979
Forks
434
Avg merge
10d 8h
Merged PRs (30d)
28

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/extensions

All issues in firebase/extensions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.