Yeah if I'm reading that right, we're indeed planning by default something like:
-- keep using our core prefect schedulers etc stack
-- spin up cloud functions or whatever, have them phone home to register under a tag like 'cloud function'
-- users would then opt-in to that tag
we're new to serverless and newish to prefect, so specifics around that would be helpful. we originally did a heavy docker stack for prefect agents b/c needed a lot of gpu etc. libs, but for the crawler, looks like we can get away with lightweight python deps, so thinking this will be more about wrangling weird cloud infra config (and afaict prefect doesn't support native plugins for running on Cloud Functions or something similar in GCP?)