Status Update
Comments
ja...@google.com <ja...@google.com> #2
de...@newelcorp.com <de...@newelcorp.com> #3
we would love to have this as well
ma...@gmail.com <ma...@gmail.com> #4
vs...@gmail.com <vs...@gmail.com> #5
[Deleted User] <[Deleted User]> #6
la...@gmail.com <la...@gmail.com> #7
so...@gmail.com <so...@gmail.com> #8
ke...@gmail.com <ke...@gmail.com> #9
I am using the Load Balancing and would really like to see that you can use a cloud functions as a backend, not only buckets and instance groups.
al...@ocoboco.com <al...@ocoboco.com> #10
[Deleted User] <[Deleted User]> #11
[Deleted User] <[Deleted User]> #12
ad...@pauloddr.com <ad...@pauloddr.com> #13
Firebase Hosting currently supports rewrites that point to a Function -- effectively giving us pretty URLs for Functions -- but it is slower by a magnitude of nearly 2x, and it also increases data transfer, probably because of Firebase's additional response headers.
I've attached a screenshot of response size and times from calling the same function directly (via
ja...@google.com <ja...@google.com>
an...@gmail.com <an...@gmail.com> #14
I have Cloud Functions REST APIs that interact with Firestore; without the ability to use my own domain to access the REST APIs is really a show-stopper. And as the above user mentioned, Firebase's performance is just not acceptable in a production environment.
st...@google.com <st...@google.com> #15
ji...@platforma.one <ji...@platforma.one> #16
Hide Functions behind Cloud Endpoints, which uses Cloud Run as API gateway and you can set a custom domain there.
Google Cloud Endpoints on Cloud Functions (
Cloud Run custom Domain (
st...@google.com <st...@google.com> #17
ha...@impact.com <ha...@impact.com> #18
ju...@sensand.com <ju...@sensand.com> #19
ko...@goodparts.org <ko...@goodparts.org> #20
ya...@gmail.com <ya...@gmail.com> #21
#20 - that is only acceptable for "public" functions without authentication (except through an API key) since Cloudfare is outside of GCP.
Next to Cloud Endpoints, there is API Gateway now which seems to be a better fit.
Googlers, is that the final word for a CNAME override, using API Gateway ? If so, case closed I guess but adding a service just for that is unnecessary overhead. Maybe it is a strategy to favor/migrate external http functions to Cloud Run - which supports custom domain.
ko...@gmail.com <ko...@gmail.com> #22
But for simpler use cases, it would still be great to have custom domain names supported natively (without Firebase, Cloud Run, or Cloud CDN) - via a CNAME.
ed...@nortical.com <ed...@nortical.com> #23
Is there any update on the progress here?
ra...@intelli-visia.com <ra...@intelli-visia.com> #24
as...@gmail.com <as...@gmail.com> #25
[Deleted User] <[Deleted User]> #26
mt...@twitter.com <mt...@twitter.com> #27
ar...@gmail.com <ar...@gmail.com> #28
ju...@gmail.com <ju...@gmail.com> #29
al...@gmail.com <al...@gmail.com> #30
to...@flexible.fi <to...@flexible.fi> #31
jo...@examind.io <jo...@examind.io> #32
v....@gmail.com <v....@gmail.com> #33
yo...@gmail.com <yo...@gmail.com> #34
vi...@gmail.com <vi...@gmail.com> #35
lu...@gmail.com <lu...@gmail.com> #36
ce...@gmail.com <ce...@gmail.com> #37
+1
[Deleted User] <[Deleted User]> #38
da...@gmail.com <da...@gmail.com> #39
ya...@gmail.com <ya...@gmail.com> #40
This has been supported with gen2 functions for a few months. Gen2 relies in Cloud Run where you can link a custom domain to the endpoint. Agreed a Googler could have said so earlier and close the issue.
bo...@weaviate.io <bo...@weaviate.io> #41
ba...@iproov.com <ba...@iproov.com> #42
se...@merrysolutions.com <se...@merrysolutions.com> #43
se...@merrysolutions.com <se...@merrysolutions.com> #44
de...@simpleclub.com <de...@simpleclub.com> #45
One solution could be to upgrade your function to v2 and attach the domain to your Cloud Run instance:
Description