As suggested here, dashboard creators might want to create their own local conda envs, and specify those when creating a dashboard. At the moment, they can only choose from a list of admin-provided global conda env names.
A new config option should allow the dashboard creator to type any conda env name, and/or ideally a full path to a conda env.
Alternative workaround: it is possible for a local conda env to work for the dashboard creator if the global list happens to contain the name of a local conda env instead of a global env.
As suggested here, dashboard creators might want to create their own local conda envs, and specify those when creating a dashboard. At the moment, they can only choose from a list of admin-provided global conda env names.
A new config option should allow the dashboard creator to type any conda env name, and/or ideally a full path to a conda env.
Alternative workaround: it is possible for a local conda env to work for the dashboard creator if the global list happens to contain the name of a local conda env instead of a global env.
Applies to any type of spawner/config.