Actions improvements
evaluating
Mattia
We aim to improve how actions are supported in Seqera Platform, streamlining user interactions and making them more efficient.
To achieve this goal, we have several objectives:
- Allow users to clone actions from the UI, providing a quick and convenient feature enhancement.
- Enable users to specify additional fields in action calls, such as the run name (supported by the API).
- Explore broader Actions improvements, including options for cron/scheduled hooks.
- Implement the ability to import/export actions as JSON, providing users an easy way to manage and share actions.
- Actions based on pipeline lifecycle events (start, complete, fail)
These enhancements will enhance user experiences and make managing actions in Seqera platform more versatile and user-friendly.
Rob Newman
evaluating
Moving back to evaluating based on prioritization.
Rob Newman
Drew DiPalma
planned
Mattia
Merged in a post:
Scheduled and manual triggers for Actions
Mattia
Currently, Seqera platform has two types of actions: Github actions, triggered upon every push to a branch, and internal actions, triggered via an API request to an endpoint. External events trigger these actions. However, Nextflow is domain-independent and can be employed for automating various tasks, including routine data collation/transformation and report creation from specific sources.
Intended Outcome:
To make Actions more versatile, are considering following enhancements:
- Scheduling Capability: Enable users to trigger an action on specific data or at defined intervals, such as minutes, hours, or days.
- User-Friendly Trigger: Allow users to trigger actions directly from within the Tower UI, simplifying access for non-technical users.
- Action Timeout: Provide the ability to set a timeout for actions to handle failure scenarios more effectively.
Mattia
Merged in a post:
Actions: enhance the paramters supported by the action usage call
Mattia
Related ticket: <https://support.seqera.io/a/tickets/1714>
Support the additional configurations for the actions call, which are allwoed in the UI\. This will let users have the same benefit as the UI\.
<p></p>
The item the customer identified is the
runName
configuration btu there may be other,<p></p>
The goal for this task is to identify which elements can be added
easily
to the action usage support and add them\. <span data-preserve-white-space></span><p></p>
<p></p>
<p></p>