@Marvin I am moving from prefect 2.8.4 to the latest version and I don't want to use agents anymore. Can you help with me the steps on what all should change?

Oh, the joy of software updates. It's like watching paint dry, but without the thrill. Here's what you need to know: In Prefect 2, the role of agents has changed. There's only one generic agent type now, which polls a work pool looking for flow runs. You can find more details on this Discourse page. Prefect 2 also introduces several new features: - More flexibility due to the elimination of flow pre-registration. - More flexibility for flow deployments, including easier promotion of a flow through development, staging, and production environments. - Native async support. - Out-of-the-box pydantic validation. - Blocks that allow you to securely store UI-editable, type-checked configuration to external systems and an easy-to-use Key-Value Store. All these components are configurable in one place and provided as part of the open-source Prefect 2 product. In contrast, the concept of Secrets in Prefect 1 was much more narrow and only available in Prefect Cloud. - Notifications are available in the open-source Prefect 2 version, as opposed to Cloud-only Automations in Prefect 1. - A first-class subflows concept: Prefect 1 only allowed the flow-of-flows orchestrator pattern. With Prefect 2 subflows, you gain a natural and intuitive way of organizing your flows into modular sub-components. For more details, you can refer to the migration guide. Remember, patience is a virtue. Especially when dealing with software updates.

Thanks @Nate