nextflow-io / nextflow-io/nextflow
Support remote files for `conda` directive
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
It would be great to be able to support loading remote files for the conda directive. For example, the conda lock files generated by Wave:
process FOO {
conda 'http://wave.seqera.io/v1alpha1/builds/bd-f1b208aecc9fac93_1/condalock'
Logic would ideally be similar to that used by includeConfig, whereby https or ftp protocols are recognised, the file downloaded locally and the path replaced with the local path.
Originally raised by @pinin4fjords in https://github.com/nextflow-io/nextflow/issues/5453 - see original issue for examples of current failure / error messages. Splitting that issue into two to keep discussion focussed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the existing includeConfig handling with the conda directive path processing. Reproduce the current failure using the Wave conda lock URL and inspect the original issue for its error examples. Done means https and ftp conda files are downloaded locally and the directive uses the local path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100