add-disabled-deployment-status - Branch - PrefectHQ/prefect

Add DISABLED to client DeploymentStatus enum for Cloud compatibility

#20244Merged

Comparing

add-disabled-deployment-status

(

2e3884f

) with

main

(

4220e18

)

Untouched: 2

Ignored: 6

Benchmarks

Passed

bench_import_prefect_flow

benches/bench_import.py

1.4 s1.4 s

bench_task_decorator

benches/bench_tasks.py

-1%

550.1 µs553.1 µs

Ignored

bench_flow_decorator

benches/bench_flows.py

Ignored

+9%

5.2 ms4.8 ms

bench_flow_call[options0]

benches/bench_flows.py

Ignored

107 ms107.4 ms

bench_task_call

benches/bench_tasks.py

Ignored

-3%

22.7 ms23.4 ms

bench_task_submit

benches/bench_tasks.py

Ignored

-1%

88.8 ms89.7 ms

bench_flow_call[options1]

benches/bench_flows.py

Ignored

107.8 ms107.7 ms

bench_import_prefect

benches/bench_import.py

Ignored

1.1 s1.1 s

Commits

Click on a commit to change the comparison range

Base

main

4220e18

-0.08%

Add DISABLED to client DeploymentStatus enum for Cloud compatibility Workers using the OSS client fail when reading deployments from Prefect Cloud that have been disabled, because Cloud returns `status="DISABLED"` but the client's enum only recognized `READY` and `NOT_READY`. This is a client-side only fix since DISABLED is a Cloud-specific feature (Cloud has a `disabled` boolean column and disable/enable endpoints that OSS doesn't have). Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

51d3009

22 hours ago

by chrisguidry

-0.18%

Merge branch 'main' into add-disabled-deployment-status

2e3884f

22 hours ago

by chrisguidry

Home Terms Privacy Docs