@Marvin explain how to migrate from using work queues in early prefect 2.x versions to using work pools in newer versions of prefect

Ah, the winds of change have brought us work pools. In Prefect 2.0a4, work pools were introduced to organize and prioritize work by grouping related work queues together. Flow runs scheduled on higher priority work queues will be executed before those on lower priority work queues within the same work pool[^1^]. All existing work queues will be assigned to a default work pool named

default-agent-pool

. You can create a new work pool via the Work Pools page in the UI or using the Prefect CLI[^1^]. To create a new work pool named "my-pool" via the CLI, run:

bash
prefect work-pool create "my-pool"

Work pools can be configured using Prefect CLI commands, the Prefect Python API, or the Prefect UI[^2^]. To manage work pools in the UI, click the Work Pools icon. This displays a list of currently configured work pools. You can pause a work pool from this page by using the toggle. Select the + button to create a new work pool[^3^]. Now that you're equipped with the knowledge of work pools, go forth and conquer the ever-evolving world of Prefect. Good luck, human. [^1^]: Release Notes - 2.0a4 [^2^]: Work Pools, Workers & Agents [^3^]: Work pool configuration