Seqera Platform Feature Requests

Is it possible to enable the estimated costs module for Azure Batch and AKS?

When Seqera Platform submits jobs to Azure Batch and encounters a 409 HTTP status code (indicating the batch quota limit has been reached), the run fails. Instead of failing, can we modify the behavior so that the platform continues attempting to submit the job until the Azure Batch pool can accept it? Caused by: Status code 409, { "odata.metadata":"https://babixanaldevm42aen.uaenorth.batch.azure.com/$metadata#Microsoft.Azure.Batch.Protocol.Entities.Container.errors/@Element", "code":"ActiveJobAndScheduleQuotaReached","message": { "lang":"en-US","value":"Active job and job schedule quota for the account has been reached.\nRequestId:e9dede46-9ab1-463b-b797-cdfee3d4db8f\nTime:2024-10-18T06:36:49.8081952Z" } } Instead of returning a 409 Status Code error and halting the run, Seqera Platform should retry submitting the job continuously until the quota is available, ensuring that the job is eventually accepted. This should be done without manual intervention and in a way that does not overload the system.

We would like to be able to authenticate to MySQL database with Microsoft EntraID due to security regulations. Entra ID Use Entra ID with MySQL database

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.

I am trying to record, track, and modify the state of my Seqera Platform instance. Its proven to be extremely difficult to adequately write out descriptions of all the settings and configurations I end up using in a simple README.md file. I have started resorting instead to the export and update functions of the CLI, such as: tw compute-envs export --workspace 1234567890 --id AbcAbcAbc > My_dev_CE_AbcAbcAbc.json tw participants list tw participants update ... tw workspaces list tw workspaces update ... tw pipelines list tw pipelines update ... While the CLI tool is invaluable for the ability to do all this Seqera Platform management from the cli, and in a potentially scripted manner, ultimately what I actually need is the ability to export all of the "configurable" components of Seqera Platform to a file, update that file as needed, and then upload it back to Seqera Platform to apply the changes. Essentially I think what I need is "Terraform for Seqera Platform", or something to that effect. Some way to not just manipulate individual aspects of the Platform but to also snapshot all of its configurations to a file that can be tracked in version-control, manipulated outside of Platform, and then used to apply the needed configuration changes to Platform. This would also have the benefit of allowing you to see the entire state of the Platform at once, instead of having to pull out single attributes one at a time. At a bare minimum, some sort of export all + import all in a YAML or JSON would help. Let me know what you think, thanks.

Similar to the (undocumented?) query params for the quicklaunch pages: my.seqeracloud.com/quicklaunch?pipeline=https%3A%2F%2Fgithub.com%2Fnf-core%2Frnaseq&revision=3.15.1&paramsText=%7B%0D%0A++++%22input%22%3A+%22foo.csv%22%2C%0D%0A++++%22outdir%22%3A+%22bar%22%0D%0A%7D&resume=false Unfortunately with quicklaunch you cannot set the rest of the parameters anymore. We need it for the launchpad/12345678910/form page (which seems to be done with formly anyway which supports pre-filling if enabled correctly).

We currently use Terraform to deploy the Seqera Platform within our AWS environment. We also use Tower CLI / Tower Forge to deploy our Amazon Batch compute environment. However, there's a manual step of having to create an access token through logging into the Seqera Platform UI dashboard and going to our profile. We would like the deployment of the Seqera Platform and the compute environment via Tower CLI / Tower Forge to be fully automated. Ideally, getting an access token needed to use Tower CLI shouldn't require logging into Seqera Platform. Could you add a programmatic way to generate an access token in a future version of Seqera Platform/Tower CLI?

When retrieving the audit logs data (from the /admin/auditlogs endpoint) there doesn't seem to be a way of filtering the returned data in any way, which means we have to grab all the audit log data and then filter the returned data. Can we add some filtering (especially on dates) so that I can, for example, only return audit log data via the API for the previous day?

When writing up processes for Launch role users I've encountered a number of problems when the features I've prototyped (tags, launch settings, etc) are unavailable to the users the process is defined for. As a a user with elevated role permissions, it would be very useful to interact with the Seqera Platform as if I were a user with the Launch role, so that I can work up processes that will work for everyone.