Seqera Platform Feature Requests

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.

It seems to be impossible to choose a version other than the default using https://seqera.io/containers/

There are a couple areas where we could use to set specific nextflow.config settings for every Nextflow pipeline that runs on a given compute environment. We could alternatively have use for being able to set config options Seqera Platform-wide. Both would be great.

As I understand it, returning the runs for a workspace using the CLI only allows us to filter with a name starts with filter. Can we add a filter that allows us to filter by run date range - e.g., only return the runs for the past day, week, etc.?

I'm trying to update from v23.2.0 to v23.3.0. When I try to run "docker login cr.seqera.io " with the credentials I was given previously, I get "Error response from daemon: Get " https://cr.seqera.io/v2/ ": unauthorized: authentication required".

As of v23.4, it is possible to get very detailed information (duration, resources) of each of the tasks comprising a workflow. However, this does not include the head job, which can also be interesting to monitor in some use cases.

Summary An important impact on users' costs is that the Platform does not use private S3 gateway endpoints for data transfer, even within the same region. As a result, users are charged with data transfer costs because the data is sent via the public internet. This also affects performance because the speed is lower than within the AWS network. Currently, it is possible to enable S3 endpont by maually creating an gateway endpoint so that AWS can ferry data directly between the instances doing the work and the bucket holding their data without that data moving via the external internet. Intended outcome Enable Seqera Platform to configure AWS compute environments to use S3 gateway endpoint as a standard configuration option. This should be possible both for manual and forge compute environments. Outcomes Improved performance and reduced costs when using AWS compute environments in Seqera Platform

Currently, when users receive mail from Seqera Platform when trying to activate a user that is not part of the trusted email list, the text is predefined for everyone and it is specific for a Cloud deployment. Edits that are required in an enterprise setting are the following: Switch the support@tower.nf mail with the TOWER_CONTACT_EMAIL value from tower.env configuration so that any support request will go to the right person Remove the text Consider registering again if you have used an anonymous email address. Alternatively, you can login via GitHub single sign-on which does not require approval. because it is most likely incorrect in Enterprise deployments. Considering the different behavior between Cloud and Enterprise deployment, the message should be clearer and explaining that the email they used to try to register is not part of trusted mail addresses and to contact the mail for instructions

Recently, I integrated an in-house pipeline in Seqera Platform/Tower launchpad. Lots of benchwork scientists are using the pipeline for NGS data analysis. Once a Pipeline run is finished, all results are saved in a Google Cloud storage bucket. The analysts can view and download any individual file via the Google Cloud console, but not download an entire folder or multiple folders. Can you add an action allowing users to download contents of a folder/multiple folders from Data Explorer?

The existing SSH credentials model poses challenges because all jobs will be using the same credentials to connect to the cluster, lacking the ability to preserve individual user identities upon HPC job submission. There is a need for a solution to preserve the user identity on the HPC side, when submitting jobs from the Platform. This functionality is crucial for system accounting, chargeback, and fair resource usage.