A custom dask config is something more advanced users might want to control in their software environments. Though it's possible to bake one in using some hacks in the post-build script, a dask_config= parameter to software environments might be a reasonable convenience to offer? (This would just add the file and set the DASK_CONFIG= environment variable.)
The bigger issue is that software environments don't currently support adding custom files or environment variables (besides making your own Docker image). So a files= and env= argument could be a more general solution, and might be a prerequisite anyway for the dask_config= convenience.
A custom dask config is something more advanced users might want to control in their software environments. Though it's possible to bake one in using some hacks in the post-build script, a
dask_config=
parameter to software environments might be a reasonable convenience to offer? (This would just add the file and set theDASK_CONFIG=
environment variable.)The bigger issue is that software environments don't currently support adding custom files or environment variables (besides making your own Docker image). So a
files=
andenv=
argument could be a more general solution, and might be a prerequisite anyway for thedask_config=
convenience.