I use Google Cloud Scheduler, https://cloud.google.com/scheduler/ , to invoke Cloud Functions (actually Firebase Functions which are really Cloud Functions under the hood).
You set up a Firebase function to run on receipt of a message to a pub/sub topic, and then in Cloud Scheduler you schedule a post to that topic.
Scheduling is easy on many levels. One could set a CICD job to do that (which is usually free in many cloud vendors).
The business value though is in data-based events. Data is inserted/updated/deleted in databases (SQL and NoSQL), event streaming, queues, identity management systems, and so on.
Until there is a way for Cloud Run to easily plug its 'functions' to those sort of events, the solution is not ready for real world use cases -- unless of course one is interested in building a whole distributed system architecture around webhooks.
I like that idea, say after N inserts to a database/bigquery or N requests to existing service, after a file is posted to storage, or once a VM variable hits a certain trigger, kick off cloud function. Great for mini batching ETLs, log cleanup/parsing, upload possessing, cache invalidation... So many use cases.
That flexibility would be great. Hope this is on the radar! Cloud run triggers. Being able to pass the event metadata in would be great too.
