View in #prefect-server on Slack
@Julian: Hey all,
we recently updated our prefect cluster from version 0.15.10 to major version 1.0.0.
We used an existing DaskCluster to distribute our flowruns, which we could simply do by setting envs
PREFECT__EXECUTOR__DEFAULT_CLASS and PREFECT__EXECUTOR__DASK__ADDRESS in our agent.
Unfortunately, this approach doesn’t seem to work anymore. I’m pretty sure we could initialize a DaskExecutor in our code
and attach it to our flow somehow, but this would be undisireable, as it requires changing each of our existing flows, but also
for each flow to come.
Is it possible to achieve the same kind behaviour as before, i.e. defining the execution engine for the agent, by simply setting 1 or 2 envs?
@Anna_Geller: The environments have been deprecated since 0.14 and in 1.0 they have been removed completely. Also, the imports for executor have changed, so instead of PREFECT__EXECUTOR__DEFAULT_CLASS it would now be PREFECT__ENGINE__EXECUTOR__DEFAULT_CLASS.
You can read more about it here
Upgrading to Prefect 1.0 | Prefect Docs
@Julian: Cool thanks, now it works. I just had to update the env names to PREFECT__ENGINE__EXECUTOR__DEFAULT_CLASS and
PREFECT__ENGINE__EXECUTOR__DASK__ADDRESS
