Seqera Platform Feature Requests

Currently, when customizing and building a Studio with conda, Wave uses a hardcoded imageSuffix naming strategy, which creates nested repository paths ( e.g., community.wave.seqera.io/data-studios/jupyter/numpy_scipy_tqdm_pip_pruned:7dc3ba408fd1df3c ). Whereas with Nextflow, Wave uses the none strategy by default. This causes issues when: Lacking ECR permissions to create repositories (ecr:CreateRepository) Needing consistency with Nextflow workflows that use different naming strategies We should enable configuration of the container image naming strategy in Wave Studios to support different registry requirements and structure constraints. I think there's two options: Env variable (specified at CE level or elsewhere) WAVE_STUDIOS_NAMING_STRATEGY=tagPrefix Configmap option (for self-hosted) wave: studios: namingStrategy: tagPrefix # none, tagPrefix, or imageSuffix

Currently, Studios cannot be used with Fusion-enabled Kubernetes CEs (Amazon EKS and Google GKE). Adding this will allow for greater control and more direct management of CEs for compliance, scale, and cost management purposes.

Many users develop their Python or R notebooks, or Nextflow pipelines in VSCode, on remote EC2 instances. Once a Studio session is in a running state, users should be able to run their local installation of the application but with the code and terminal running in the remote Studio session via a SSH tunnel to the EC2 instance. There is a VSCode plugin available that can be reviewed for inspiration.

Devcontainers is a standard format developed by Microsoft to configure development environments for VSCode and GitHub codespaces . It’s also going to be supported by GitPod . It’s a JSON file that sits in the root of a repo in a directory called .devcontainer/ . It can contain VSCode extensions, etc but the key things are: Dockerfile, docker arguments, and launch run commands. Supporting these files in Studios allow users to programmatically encode settings for Studios using a well adopted standard.

Adding the ability to programmatically execute commands in running Studio sessions remotely would allow deeper integration into other products/features both across Seqera Platform and third-party applications/tools.

Within a running private Studio session, automatically use existing Git user credentials attached to the user to authenticate to a remote Git repository (e.g. Github, Gitlab, Bitbucket, Gitea).

When creating a Studio sessions, it is possible to associate key-value resource labels to the session. These resource labels are displayed in the UI as tags, but the list of Studios does not provide the ability to filter or sort the studios based on the key or value of these labels. For larger workspaces with many studios, it would be helpful to subset the available sessions to those with particular keys and/or particular values.

Once a Studio session is running, it incurs costs. Estimating the hourly cost of the session and clearly presenting that in the user interface will ensure that users are aware of the potential cost impacts. The estimated hourly cost could initially be estimated on the “Add Studio” page (when the CE is selected) and be displayed on the specific Studio session detail page once the session is in a running state. When the session is in a stopped state, the cost estimator is still visible, but considered inactive.

In the "About" tab of a completed task, it would be nice to have a link to launch a studio environment using the same image, and with the input data linked/copied into the environment. It would be a convenient way to quickly test different settings on a given step/tool.

We would like to store 3-5 pre-built docker images in the dropdown with custom, user-friendly names for each. Our users would much prefer to interact with known, user-friendly names rather than docker URIs.