Seqera Platform Feature Requests

Although the Open API docs exist, there are no details on the fields themselves (e.g. when to use it, why to use it, what are its limitations etc) that could provide information about the nf-tower maps and their field limits and size.

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?

I ran openapi-python-client to generate a Python package from the OpenAPI spec. I got the following warnings, which suggests that the definition file is not fully valid: WARNING parsing POST /compute-envs within default. Endpoint will not be generated. Could not find reference in parsed models or enums WARNING parsing GET /data-links within default. Cannot parse response for status code 200 (Could not find reference in parsed models or enums), response will be omitted from generated client Reference(ref='#/components/schemas/DataLinksListResponse') WARNING parsing GET /data-links within default. Cannot parse response for status code 202 (Could not find reference in parsed models or enums), response will be omitted from generated client Reference(ref='#/components/schemas/DataLinksListResponse') WARNING parsing POST /data-links within default. Cannot parse response for status code 200 (Could not find reference in parsed models or enums), response will be omitted from generated client Reference(ref='#/components/schemas/DataLinkDto') WARNING parsing GET /data-links/{dataLinkId} within default. Cannot parse response for status code 200 (Could not find reference in parsed models or enums), response will be omitted from generated client Reference(ref='#/components/schemas/DataLinkResponse') WARNING parsing PUT /data-links/{dataLinkId} within default. Cannot parse response for status code 200 (Could not find reference in parsed models or enums), response will be omitted from generated client Reference(ref='#/components/schemas/DataLinkDto') WARNING parsing GET /workflow/{workflowId}/launch within default. Cannot parse response for status code 200 (Could not find reference in parsed models or enums), response will be omitted from generated client Reference(ref='#/components/schemas/DescribeWorkflowLaunchResponse') Unable to process schema /components/schemas/ComputeEnv_ComputeConfig_: Cannot take allOf a non-object Failure to process schema has resulted in the removal of: /components/schemas/ComputeEnv_ComputeConfig_ /components/schemas/CreateComputeEnvRequest /components/schemas/WorkflowLaunchResponse /components/schemas/DescribeWorkflowLaunchResponse Unable to process schema /components/schemas/DataLinkDto: Cannot take allOf a non-object Failure to process schema has resulted in the removal of: /components/schemas/DataLinkDto /components/schemas/DataLinkResponse /components/schemas/DataLinksListResponse

Last weekend, we had a rare anomaly in which all Nextflow workflows silently "stalled". I've written code to identify workflows in this condition using the Seqera Platform API . Next I want to cancel and resume the workflows. Cancel is straightforward and it's also easy to Resume via the Seqera Platform/Tower web UI by selecting Resume from the kebab menu on the right-hand side. But what is a good way to do this via the Seqera Platfom API? We use the /workflow/launch endpoint to initiate workflows. When a workflow is cancelled, Seqera Platform/Tower should have all the information to immediately resume the workflow since it was passed by the initial API POST request. As I understand the API, the workflow/launch endpoint has a Boolean resume attribute and I see no alternative. It seems rather long-winded to query the API and use those values to repopulate all the payload attributes for the workflow/launch endpoint, set resume to True and send all this back to the endpoint. Is this the recommended approach or is there a better alternative?