Currently when you configure a single pipeline in Tower / Platform, there is a field where you can supply extra Nextfow config options for the pipeline that would be included in the pipeline's nextflow.config file. It would be very helpful if we could instead have our own collection of separate config files that could be registered with Tower and easily applied to all desired pipelines, globally. For example, right now I am updating the config for the nf-prov plugin in our pipelines; I currently have to modify the nextflow.config file in every single pipeline repo in our organization in order to update the settings for all pipelines, and I have to copy/paste the same config into every one of them. It would be a lot easier if we could have for example a single "plugins" config file, saved on the Tower server, which could be updated, and then have that extra config file used for all pipelines on Tower where we would like to use the updated nf-prov settings. Similarly this would extend to all other settings saved in the nextflow.config files across all our pipelines; we could reduce code duplication and update all configs at once if we could just save them as single extra config files to be applied by Tower at runtime. Perhaps such a feature does not need to be only for Tower / Platform either, it might be helpful to be able to do this from the command line as well, the same way that we can use a git repo URL as the Nextflow script argument to nextflow run , could probably implement this allowed the nextflow -c and -C args to accept a URL to config files hosted on a git repo. This would allow us to maintain a dedicated git repo just for global configs and then easily use them in both Tower and from cli. ----- edit: for clarification, it is possible to use S3 and HTTP file paths with the includeConfig nextflow.config directive when running from the command line, however this does not work from Nextflow Tower / Seqera Platform since the Launchpad does not support AWS authentication.
