Andrew Maturo
07/25/2024, 10:15 PMMarvin
07/25/2024, 10:15 PMprefect.yaml
does not automatically overwrite existing work pools. Instead, the system checks if the specified work pool exists. If it doesn't exist, you will encounter an error stating that no worker will be able to pick up the runs because the work pool is not found.
For example, attempting to deploy a flow to a non-existent work pool will result in:
This deployment configuration references work pool 'non_existent_pool' which does not exist. This means no worker will be able to pick up its runs. You can create a work pool in the Prefect UI.
For advanced customization, users can update work pools via the Prefect CLI or Prefect UI.
You can refer to the following links for more detailed information:
- Concepts - Work Pools
- Tutorial - Work Pools
GitHub Issues of interest:
- Deployment configuration references non-existent work pool
- Saving inputs when using existing deployment configuration
Let me know if you need further clarification.