Add ability to install a subworkflow composed nf-core and non-nfcore modules/subworkflows.

[kenibrewer]

Description of feature

As a maintainer of a non-nfcore modules library, I would like to be able to install my custom subworkflows composed of nf-core modules/subworkflows and non-nfcore modules/subworkflows into a nextflow pipeline using the following command:

nf-core --git-remote https://github.com/kenibrewer/nf-modules-demo --branch main subworkflows install demo_subworkflow

This is blocked by the fact that the ComponentInstall class assumes that all the modules/subworkflows are coming from the same modules library when instead they could be coming from different org_names and branches.

This will allow me to modularize and version re-usable subworkflows for use in my organizaiton.

Still putting together the demo subworkflow that will trigger the errors I was seeing. I'll report back when I have that.

[kenibrewer]

@ewels Here is the other issue that is a problem for creating private modules repos.

[mirpedrol]

Hi @kenibrewer,
@jvfe is currently working on adding a new feature to allow subworkflows with modules from different remotes, you can see the open PR #3083

[awgymer]

and version re-usable subworkflows

One of the big weaknesses of subworkflows in general and these cross-repo subworkflows is that I don't think there is good versioning.
The subworkflows install and subworkflows update will always enforce you installing the most recent version of any module within that subworkflow.

This makes it functionally impossible to fix a subworkflow on specific module versions which may or may not differ from those in the wider workflow and which may or may not break the subworkflow (i.e. if the expected input channel shapes change for a module)