Seqera Platform Feature Requests

We're trying to track down an issue where our registered pipeline specs (specifically the git revision) are changing and we don't know why. I checked the audit logs, and they capture pipeline creation, but not pipeline updates. This is audit-log-worthy - which repo and what revision a pipeline runs controls what code a Nextflow user runs when they use a pre-defined pipeline, so changes to that are of interest for security reasons.

In Seqera Platform there is a handy Audit Log under the Admin Panel. However, a lot of times we are trying to debug things related to how Seqera Platform is interacting with our AWS account in order for it to configure and provision resources, and it gets very difficult to clearly understand what Platform is doing with our AWS. For example, you click some buttons in the Platform UI, then Platform does some things with AWS, and maybe it works or maybe it gives an error, but ultimately you dont actually know all of the actions it just took, or attempted to take. It would be really helpful if you could simply see this in an audit log that listed clearly all these actions that the Platform is taking against the AWS API. This could of course be extended to include other cloud and HPC back-ends that Platform is interacting with. I saw in some old documentation that there may have been some environment variables that you could export when deploying Platform in order to enable it to use more verbose logging on its deployment server, but that kind of functionality is not really helpful because you would need to shut down the entire Seqera Platform deployment just to toggle such env vars. It would be simpler and easier if some amount of this sort of logging was just already available in Platform itself. I think if we had this sort of AWS audit log available from within Platform, it would also help a lot in that I could debug my own issues a lot easier instead of having to submit so many Support tickets.

We are migrating a couple of workspaces to a new organization. We like to migrate everything in the workspace, including, users, workflows, compute environment, and the history of the runs. Do you have any recommendations on how to do this? It seems that we can do most of these resources apart from migrating the history of the runs. Is there any workarounds?

Users frequently request the ability to associate cloud service provider tags with workflow runs. This feature aims to annotate resources utilized by workflow runs with cloud-specific tags, enhancing monitoring and tracking capabilities from the cloud provider's administration console. The current limitations include the inability to add tags to Seqera Platform elements in shared workspaces. Additionally, resource labels lack parametric behavior, making it challenging to track users and individual workflows for cost reporting. The proposed change is two-fold: Add resource labels to items in shared workspaces. Introduction of template resource labels, allowing fixed names with flexible values at launch (e.g., user name or workflow id). This enhancement significantly improves tracking capabilities and management experience. Implementing these enhancements aligns the tagging system with user expectations, providing a more flexible and powerful solution for resource annotation and tracking

We would like to monitor when collaborators are added to a workspace. As far as I can tell, the audit log information tells us who added the participant (via the principal field, which corresponds to a user ID), but I can't see how we can tell who was added.

For accounting purposes, we must tag all resources created by Nextflow and Nextflow AWS Batch jobs with the username of the user who created the job. We need the tag to be called billing and the username of the user to be the value. We also need to tag all resources created by Forge with some identifying tag so that we can tune the permissions, i.e. so that we're not giving Nextflow permissions to destroy EFS filesystems used by the entire company and with vital data on them. For accounting, we require that all resources created by NextFlow, including Spot instances, S3 buckets, compute environments, and anything that costs money, to be tagged with the username of the user who ran the job.

In the current Seqera Platform setup, system configuration is primarily managed through a YAML file, necessitating a system restart for changes to take effect. To enhance the flexibility and responsiveness of system administration, we propose a feature that enables real-time configuration adjustments without the need for a system restart: Admin-Friendly Configuration: Introduce a dedicated interface, accessible through Seqera Platform > Admin > System Options , facilitating the seamless configuration of the system. Dynamic Storage: Utilize the SysOption entity to store and manage these configuration options, allowing administrators to apply changes instantly without needing to restart

After a pipeline completes on Seqera Platform it can be tricky to clean up execution work folders (to save space) while preserving useful log files. This workflow could be improved by enabling Seqera Platform/Nextflow to send all logs to separate storage – outside of the pipeline run work folder, but still accessible by Seqera Platform.

We ran into some issue where the behavior of the user permissions differed significantly from what we expected and want to clarify if its intended behavior or a misconfiguration or bug on our side. First, It looks like users ordinary/non-admin users are able to create organizations at will. Is this intended functionality and if it is, is there a way to stop it? Second, When we add a user to an organization are they supposed to be able to see all the shared workspaces in it? Because right now when we add users to orgs they don't see any workspaces they aren't explicitly added to.