my prefect server setup prefect-metrics.waow.tech
python orchestration
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

override command to uv run prefect flow-run execute

the pull step creates a .venv with python 3.14 via uv sync, but the
default command (prefect flow-run execute) runs with the system python
3.11 which can't find the .venv packages. overriding command to
uv run prefect flow-run execute makes the flow subprocess use the
.venv python 3.14 where all deps are installed.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

zzstoatzz 7ff3f059 b4f6f47b

+10
+10
prefect.yaml
··· 12 12 entrypoint: flows/diagnostics.py:diagnostics 13 13 work_pool: 14 14 name: kubernetes-pool 15 + job_variables: 16 + command: uv run prefect flow-run execute 15 17 schedules: 16 18 - cron: "*/5 * * * *" 17 19 ··· 19 21 entrypoint: flows/gh_notifications.py:gh_notifications 20 22 work_pool: 21 23 name: kubernetes-pool 24 + job_variables: 25 + command: uv run prefect flow-run execute 22 26 schedules: 23 27 - cron: "0 * * * *" # hourly 24 28 parameters: ··· 28 32 entrypoint: flows/tangled_items.py:tangled_items 29 33 work_pool: 30 34 name: kubernetes-pool 35 + job_variables: 36 + command: uv run prefect flow-run execute 31 37 schedules: 32 38 - cron: "0 * * * *" # hourly 33 39 ··· 35 41 entrypoint: flows/enrich.py:enrich 36 42 work_pool: 37 43 name: kubernetes-pool 44 + job_variables: 45 + command: uv run prefect flow-run execute 38 46 concurrency_limit: 1 39 47 schedules: 40 48 - cron: "5 * * * *" # 5 minutes after gh-notifications ··· 43 51 entrypoint: flows/cleanup.py:cleanup 44 52 work_pool: 45 53 name: kubernetes-pool 54 + job_variables: 55 + command: uv run prefect flow-run execute 46 56 schedules: 47 57 - cron: "0 2 * * 0" 48 58 parameters: