-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Support functions region #1874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'll get this in 5.1, thanks for pointing it out! |
Hi @jamesdaniels! Is it available now? |
Released in |
this is not working for europe-west1. Without setting them to europe-west1 it works fine but when I update my functions location, REGION in app.module.ts and rewrites in firebase.json, I get CORS errors on all my callables |
See if you're actually deploying in |
Default GCP resource location: eur3 (europe-west), I don't know where else I can check this? |
Confirmed not working globally. When using dependency injection this doesn't work: imports: [
...
AngularFireModule.initializeApp(environment.firebase),
AngularFireFunctionsModule,
]
providers: [
...
{
provide: REGION,
useValue: 'europe-west1',
}
] and use: firebase.functions().httpsCallable(... The above still sends Function calls to But if I do it at the function level it works: firebase.app().functions("europe-west1").httpsCallable('... |
There doesn't seem to be anyway to configure the region or url for a firebase function, the URL appears to be hardcoded to
us-central1
. It is possible with the underlying firebase SDK through the functions constructor but I can't see anywhere that is exposed in angularfire.Regions are fairly new so I guess this is yet to be implemented in angularfire?
Version info
Angular: 6.1.7
Firebase: 5.4.2
AngularFire: 5.0.0
The text was updated successfully, but these errors were encountered: