Open ahuang11 opened 1 year ago
If you do @flow(task_runner=DaskTaskRunnerConfig.load("foo").create_task_runner())
it'll work since we execute the script at runtime.
We'll probably want to explore a real first-class pattern for this, maybe we can find a way to get this in people's hands without committing to it as the final pattern.
This is very interesting!
Definitely worth exploring a first-class pattern since it could make the configuration of task runners easier. Could we create a type of block similar to an infra block where it's job is to store config and create a specific type of task runner? If we could, it would probably involve creating a new block capability and adding a new task argument to accept those types of blocks.
Probably other ways to approach this, but this definitely worth exploring!
Could we create a type of block similar to an infra block where it's job is to store config and create a specific type of task runner?
I've talked about this before, but basically I think that task runners should become WorkerInfrastructure
blocks. You'd then just specify @flow(worker_infrastructure="dask-cluster/foo")
Originally from Evgeny:
However, I wonder how this would work, if it's inside a flow?