Seqera Platform Feature Requests

At the moment, you can select multiple pipelines in the Run page and then "Delete selected". Can this be expanded to also cancel multiple workflows? Use case would for example be, something is broken on the CE side and all pipelines submitted to that CE need to be cancelled

Seqera Platform currently allows users to configure the launchContainer that runs the Nextflow head job in a limited number of ways: Enterprise Deployment Configuration (Seqera Platform Enterprise only) Custom Nextflow Launcher images can be specified in the deployment configuration ( docs ) Note: Modifying this image requires Platform node restarts API-Level Launch Container Specification (Enterprise & Cloud) The launchContainer parameter in the Create Action API endpoint allows you to set the orchestrator image for pipelines triggered via Seqera Actions. The launchContainer parameter in the Create Pipeline API endpoint allows you to set the orchestrator image for pipelines triggered via UI launchpad entries. The launchContainer parameter in the Launch Workflow API endpoint allows per-workflow orchestrator image specification. These parameters are currently accessible only via the API and our Terraform provider. There is no corresponding UI option, which forces users to rely on the API for a core part of pipeline, action, and launch configuration. Proposed Solution 1 Add a launchContainer option to the Create Pipeline page Add a launchContainer option to the edit pipeline page Add a launchContainer option to the Create Action page Proposed Solution 2 In terms of platform usage, it probably makes more sense to set the launchContainer at the compute environment level. This matches the needs of large pharma customers that need to customize proxies and networking certificates used in these launchContainers .

It is hard to find out the version of each tool for the docker images that contain multiple tools (e.g., community.wave.seqera.io/library/htslib_samtools_star_gawk:de8c848656c2c4c5 ). So whether it's possible to include the versions of multiple tools directly in the image name (just like community.wave.seqera.io/library/fastp:0.26.0--7c8c3de6c8d83060 ). Or add a column on the download webpage ( https://community.wave.seqera.io/repo/library/htslib_samtools_star_gawk ) to display the versions of the tools included in the Docker image. Thanks

The nf-core website renders Strings that are validated via a pattern at the bottom of the help text (see screenshot, for example this sarek parameters tools : https://github.com/nf-core/sarek/blob/500ef3eb5d79a7037bd6a111ffcc1d79895c3b8d/nextflow_schema.json#L114 ). It would be great to incorporate this into the Launchform on Platform as well. Currently, to obtain the full list of allowed string patterns, I must either intentionally mistype and trigger the validation or leave the platform to check the parameter on the nf-core website. website code here: https://github.com/nf-core/website/blob/1ed0d3efc092303725ea58e2db7add334aaf9f4b/sites/main-site/src/components/schema/SchemaListingElement.svelte#L12

Currently, users with launch permissions can't launch pipelines and modify the revision. That would be a useful feature for us, specifically for users launching via tw/seqerakit/api. For example, one approach would be to have a way to indicate in a pipeline that the revision should be flexible for users with launch permissions.

Platform currently supports parameters that are simple types (strings, numbers, etc), but Nextflow supports more complex parameters via the params-file argument. These can be arbitrarily nested maps and lists. Currently workflows that expect this type of parameter will not be able to take those parameters in Platform due to the restrictions on parameter type. It would be helpful if users could specify these parameters in Platform without removing the schema.json .

Currently there are two ways to launch a pipeline via the API: Populate the body of a POST /workflow/launch request , which requires getting a number of details such as the compute environment and configuration Create an action and POST /actions/${actionId}/launch , which only take pipeline params as options It would be nicer to reconcile the two and have a simpler flow: Create pipeline on Seqera Platform Launch specified pipeline using an endpoint, e.g. POST /pipeline/${pipelineId}/launch Importantly you would only be able to modify a very limited subset of options with this option, e.g. the pipeline parameters. This would save the automation developer the time and effort in writing a number of requests to GET settings before launching a pipeline via automation. The revision, compute environment, working directory, staging options and many other settings would be fixed and require addition of a new pipeline for a launch. This has some overlap with some other feature requests such as: API equivalent of this feature request

Some of our long running workflows eventually fail with the error: Error when retrieving credentials from container-role: Error retrieving metadata: Received error when attempting to retrieve ECS metadata: Connect timeout on endpoint URL: "http://XXX.XXX.XXX.X/v2/credentials/XXXXXXXXXXXXXXXXXXXXX" (Specific info redacted) We would like to implement the fix described here . Is there an easy way to add that line to the launch template using Tower Forge? I know it is possible to create a custom AMI that includes some variation of those instructions, but that's a lot of work and I thought I'd check if there's an easier way to solve the problem first.

Similar to Ken's request [1] - but for users who might need to use a custom AMI that already has aws cli installed, they would need to modify the launch template to remove the Batch Forge commands which reinstall the aws cli. To go beyond simply appending to the launch template, it would be helpful to give users the option to specify an existing custom launch template. This would mirror the approach we currently provide that allows users to provide the IDs for existing IAM roles during Batch Forge CE creation. [1] https://feedback.seqera.io/feature-requests/p/more-flexibility-in-tower-forge-ability-to-add-lines-to-launch-template

Add fine-grained role/permission controls and pass-through credentials so Studio sessions honor per-user permissions. Additionally, when mounting data specify each mount point as either read or read+write