POC: Support pipeline archives instead of git repos or local paths #6093
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds support for using archives of pipelines instead of git repos for remote use. This is useful because it bypasses remote git which can be problematic in secure environments or when hitting rate limits. To use, you can run `nextflow run https://url.com/path/to/archive.tar.gz` which will download the files to artefacts and run them. We could imagine something like Seqera Platform serving secure URLs to Git archives to allow users to use a repo without granting them access to the repo itself. The main downside of this is it might encourage bad practice, where users will use this in preference to a Git repo where they should do the majority of their work. Signed-off-by: adamrtalbot <[email protected]>
✅ Deploy Preview for nextflow-docs-staging canceled.
|
|
Between this and the plugin registry, we're just getting closer and closer to a pipeline registry... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for using archives of pipelines instead of git repos for remote use. This is useful because it bypasses remote git which can be problematic in secure environments or when hitting rate limits. To use, you can run
nextflow run https://url.com/path/to/archive.tar.gzwhich will download the files to artefacts and run them. We could imagine something like Seqera Platform serving secure URLs to Git archives to allow users to use a repo without granting them access to the repo itself. The main downside of this is it might encourage bad practice, where users will use this in preference to a Git repo where they should do the majority of their work.Supporting artefacts instead of cloned repos is an idea I've been noodling around with - it might provide another way to deploy and manage collections of pipelines in Nextflow where we don't have to treat everything as a Git repo.
I'm aware this is pretty crude.