Seqera Platform Feature Requests

Please provide an API endpoint that returns the current version of the API. This allows for simple, automated tracking of API version for callers and is critical for repeatability/reproducibility.

It would be helpful to be able to shortcut from the Reports tab directly to Data Explorer, either to download a file that is too big to be downloaded from Reports or to further explore the results directory.

Users who have Azure Data Lake Storage (ADLS) should be able to use Data Explorer for selecting data sources for Nextflow pipeline Runs and Studio sessions.

Currently, all workflows in a shared workspace are shared with the entire organization. It would be helpful to provide more fine-grained sharing controls that allow both 1) a central way to modify/adjust pipelines across multiple workspaces 2) specific sharing options that provide access in a subset of the organisation's workspaces

I tried to build a container with this Bioconda package which has been online for more than 4 months: https://anaconda.org/bioconda/esme_mpich_4_2_3 but there is an error message indicating that it is not found (whereas I can install it on my laptop with conda). I guess that the Seqera Wave database or channel synchronization may not be up to date. Can you help sort it out?

If a workDir is not defined in the Launch API endpoint, fallback to the workDir set in the compute environment instead of returning an error "Missing workflow launch work directory" Currently, you can set the following on the compute environment, but these are not being picked up by the workflow when launched: workDir preRunScript postRunScript

Currently we have no way to integrate with GitHub Apps to allow for checking out of GitHub repositories. This means we need to use a full fledged GitHub account with a personal-access-token which can be a security risk as the account would only be used for Seqera Tower. This also makes us burn an organization wide account seat because of this limitation. We do not want to tie this access to a single user as we then have to update the GitHub access token after the person leaves. Please add support for GitHub Apps to checkout repositories instead of a full GitHub account + personal-access-token.

We would like the ability to use multiple Azure Blob Storage Accounts in Nextflow with the az: syntax. Storage accounts within Azure each have their own unique credentials that are required by the Seqera Platform to access the storage account. Additionally, the Platform can only currently support one credential per compute environment, setting a hard limit on 1 CE only being able to access a single storage account based on the credential.

Now that Wave is using Postgres as its backend, it would be nice to be able to consolidate down to one database. Support for using Postgres in Nextflow Tower would allow us to consolidate a bunch of our infrastructure - it's one of our only apps using MySQL/Maria

A research project might cut across multiple pieces of the Seqera stack. A project might include Data inputs: The original input datasets Runs: One or more Nextflow runs Data outputs: Data files and associated metadata written as outputs from those runs Studio sessions: Both templates and active sessions used for interactive analysis of those datasets Provenance connecting these pieces together. At the moment, some layers of the stack have the ability to segment (tags on Pipelines, tags on runs, etc) but it would be helpful if a user can group these elements together into the concept of a "project".