Hi all,
in older Nextflow versions, e.g. 24.04.4.5917, conda environments that were automatically created from a yaml file were named by the main tool installed. This looks like bioawk-7367e7bd91fa22bd7f881a5a45309d8e and was very handy while debugging processes in pipelines as the respective environment that was used by the pipeline could be used in an interactive process without a lot of searching in the conda env folder.
With version 24.10.2.5932 the naming scheme seems to have changed as they are all named like env-2973040e71f07a45-c5befc178419489e841c29b029f09e1b.
Is there any way to restore the old naming pattern with the new nextflow version? Putting a name tag in the yaml file seems not to work.
cheers,
Oliver