fix(storage-resize-images): kit/extension parity – BUCKET_REGION offers europe-north2 and northamerica-south1, which can't deploy
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- firebase, typescript
- Domain
- cloud
Research direction
Read kits/storage-resize-images/src/config.ts around lines 71 and 85 and compare the BUCKET_REGION choices with the Cloud Functions locations list mentioned in the issue. Remove the two unsupported options or map them to supported regions, following the existing multi-region mappings; done when neither choice can cause this deployment failure.
Written by the indexing model from the issue text.
Description
storage-resize-images kit/extension parity. Priority: medium. Two BUCKET_REGION choices can never deploy.
Difference
BUCKET_REGION offers europe-north2 and northamerica-south1, but neither is a Cloud Functions location. They are the only two of the kit's regions missing from the project's Cloud Functions locations list. The extension has no BUCKET_REGION param.
Reproduced
With BUCKET_REGION=europe-north2:
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.
The CLI first prints its "Verify that your project has a Google App Engine instance" hint, which points the wrong way, and the whole deploy aborts, including other functions in the same firebase.json. northamerica-south1 was checked against the locations list only, not deployed.
Code
- Kit: config.ts#L71, #L85.
Resolution
Remove both options, or map them to the nearest region Cloud Functions supports, as the multi-region options already are.
- Dominant language
- TypeScript
- Stars
- 978
- Forks
- 433
- Avg merge
- 21h 58m
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/extensions
-
decision(storage-resize-images): kit/extension parity – ALLOWED_EVENT_TYPES is ignored, the kit reads EXT_SELECTED_EVENTSPossibly taken A pull request linked to this issue is open or already merged. Opendecision kits
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
firebase/extensions#3273 ·
Maintainers usually reply within 1 day
-
docs(storage-resize-images): kit README's Multiple instances section fails in an installed projectOpenkits type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
firebase/extensions#3271 ·
Maintainers usually reply within 1 day
-
kits type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
firebase/extensions#3270 ·
Maintainers usually reply within 1 day
-
fix(storage-resize-images): kit/extension parity – onCompletion event no longer carries the object namePossibly taken A pull request linked to this issue is open or already merged. Openkits type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
firebase/extensions#3266 ·
Maintainers usually reply within 1 day
-
fix(delete-user-data): kit/extension parity – spaces in EXT_SELECTED_EVENTS silently drop eventsPossibly taken @CorieW claimed this 3 days ago. Openkits type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
firebase/extensions#3259 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in firebase/extensions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
db-ux-design-system/core-web#8613 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug:new
Difficulty 1/5 Under an hour Newbie friendliness 78/100
callstackincubator/simlock#934 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gchq/LD-Explorer#286 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
foxglove/mcap#1907 · 1 comment ·
Maintainers usually reply within 1 day