From a78dab106f39867d82feb9b9a9b68522b0c7f405 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" <179508745+promptless[bot]@users.noreply.github.com> Date: Fri, 15 Nov 2024 04:55:57 +0000 Subject: [PATCH] Revert previous docs update --- docs/3.0/get-started/quickstart.mdx | 5 ++--- docs/3.0/resources/upgrade-agents-to-workers.mdx | 8 -------- 2 files changed, 2 insertions(+), 11 deletions(-) diff --git a/docs/3.0/get-started/quickstart.mdx b/docs/3.0/get-started/quickstart.mdx index 06d2cfe3cc47..a248585231eb 100644 --- a/docs/3.0/get-started/quickstart.mdx +++ b/docs/3.0/get-started/quickstart.mdx @@ -122,8 +122,6 @@ python my_gh_workflow.py Prefect automatically tracks the state of the flow run and logs the output, which can be viewed directly in the terminal or in the UI. -There are no changes between the original content and the proposed changes. Therefore, the content remains the same. - ## Create a work pool Running a flow locally is a good start, but most use cases require a remote execution environment. @@ -166,10 +164,11 @@ Deploy your flow to Prefect Cloud using a managed work pool. 1. View your new work pool on the **Work Pools** page of the UI. - + You can also choose from other [work pool types](https://docs.prefect.io/concepts/work-pools/#worker-types). + ## Deploy and schedule your flow A [deployment](/3.0/deploy/infrastructure-examples/docker/) is used to determine when, where, and how a flow should run. diff --git a/docs/3.0/resources/upgrade-agents-to-workers.mdx b/docs/3.0/resources/upgrade-agents-to-workers.mdx index 184b961d06c7..4ad1d5738595 100644 --- a/docs/3.0/resources/upgrade-agents-to-workers.mdx +++ b/docs/3.0/resources/upgrade-agents-to-workers.mdx @@ -32,9 +32,6 @@ from that pool. - Improved visibility into the status of each worker, including when a worker was started and when it last polled. - Better handling of race conditions for high availability use cases. -- New filtering capability with `WorkerFilterStatus` that allows for the inclusion or exclusion -of specific worker statuses, simplifying deployment by suppressing unnecessary setup instructions -in environments with active workers. ### Work pools @@ -91,11 +88,6 @@ to enable [dryer deployment definitions](/3.0/deploy/infrastructure-examples/doc file or use the [`deploy`](/3.0/deploy/infrastructure-examples/docker) function. -5. **Deployment process improvements:** - - Deployment scripts now check for active workers in a work pool before displaying setup instructions. - This ensures that unnecessary instructions are not shown when active workers are present, - streamlining the deployment process and improving user experience. ## What's similar - You can set storage blocks as the pull action in a `prefect.yaml` file.