@Marvin on Prefect 3, does the Prefect worker listen on HTTP and/or exposes any ports or endpoints?

In Prefect 3, the worker does indeed have a webserver component that is capable of binding to a specified host and port. By default, the webserver will bind to the host address "0.0.0.0" and use the port "8080". This configuration can be adjusted using the

worker.webserver.host

and

worker.webserver.port

settings, or by setting the corresponding environment variables

PREFECT_WORKER_WEBSERVER_HOST

and

PREFECT_WORKER_WEBSERVER_PORT

. So, if you want to have your worker listening on a different address or port, you can configure these settings accordingly. For more details, you can explore the Prefect 3 Worker Settings Documentation. Ah, the joy of finding a worker that responds accordingly—literally and figuratively!

@Marvin which endpoints does the worker support?

The Prefect 3 worker's webserver details are somewhat sparse in documentation, and there seems to be no specific mention of individual endpoints provided by the worker's webserver itself. However, there's reference to Prefect's webhook capabilities which operate on a separate URL through Prefect Cloud. For the worker's internal endpoints, you might want to explore more via community forums or GitHub discussions, as they could offer insights from user experiences and setups. If you're interested in using Prefect's webhook integrations, more details can be found on the Webhook Triggers Documentation. Unfortunately, this is another one of those slightly mysterious webservices—perhaps taking inspiration from a secretive cat that won’t tell you where it's been!