So if you set up a Cloud Function to be triggered by PubSub then it is set up as a Background Function, and TIL that background functions have additional limitations on available quota. If you want to set up a Cloud Function as an HTTP endpoint to be triggered by a PubSub push subscription, you can do this but you would need to verify the URLs independently for each function.This then begs the question, if I set up a Cloud Function to be an HTTP endpoint, its URL is namespaced by the region and project ID, and so why do I need to verify the domain/url for the function since it can only have that URL if it were created in this project? This forces manual intervention and stops you from being able to programmatically provision push subscriptions to Cloud Function HTTP endpoints making the overall process quite tedious.
--
You received this message because you are subscribed to the Google Groups "Google Cloud Pub/Sub Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cloud-pubsub-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cloud-pubsub-discuss/10959a8c-7233-47ba-bd8d-a5bb9f685a8e%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cloud-pubsub-discuss/CAKdozMfhTt5Qam37pqez9PJQ2HPKztA36xGTcDt8w7EfnErD7Q%40mail.gmail.com.