You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently integrating various workflows within our CI/CD processes and have come across a limitation within the VelaUX interface that I would like to bring to your attention. Our team frequently utilizes the command line interface (CLI) to directly issue as it is not supported well in VelaUX(hard to use). While this workflow fits well into our automation strategies, we have noticed that these directly distributed WorkflowRun objects are not visible or manageable from the VelaUX user interface.
Issue Details:
Current Behavior: When a WorkflowRun object is initiated directly through the CLI, it does not appear in the VelaUX dashboard. This makes it challenging to track the status and view logs for these runs within the unified interface that VelaUX provides.
Expected Behavior: We would like the VelaUX dashboard to support the visibility of all WorkflowRun objects, regardless of whether they are initiated via the VelaUX UI or directly through the CLI. This would greatly assist in maintaining a cohesive view of all workflows, their status, and results.
Proposed Solution:
Develop functionality within VelaUX to poll or receive updates regarding WorkflowRun objects created via the CLI.
Ensure that these objects are displayed in the same manner as those initiated through VelaUX, including necessary details such as status, duration, and access to logs.
Provide filtering and search capabilities within the dashboard to allow users to easily differentiate and locate WorkflowRun objects based on their source of initiation (CLI vs. VelaUX UI).
The text was updated successfully, but these errors were encountered:
Hello VelaUX Team,
I am currently integrating various workflows within our CI/CD processes and have come across a limitation within the VelaUX interface that I would like to bring to your attention. Our team frequently utilizes the command line interface (CLI) to directly issue as it is not supported well in VelaUX(hard to use). While this workflow fits well into our automation strategies, we have noticed that these directly distributed WorkflowRun objects are not visible or manageable from the VelaUX user interface.
Issue Details:
Current Behavior: When a WorkflowRun object is initiated directly through the CLI, it does not appear in the VelaUX dashboard. This makes it challenging to track the status and view logs for these runs within the unified interface that VelaUX provides.
Expected Behavior: We would like the VelaUX dashboard to support the visibility of all WorkflowRun objects, regardless of whether they are initiated via the VelaUX UI or directly through the CLI. This would greatly assist in maintaining a cohesive view of all workflows, their status, and results.
Proposed Solution:
Develop functionality within VelaUX to poll or receive updates regarding WorkflowRun objects created via the CLI.
Ensure that these objects are displayed in the same manner as those initiated through VelaUX, including necessary details such as status, duration, and access to logs.
Provide filtering and search capabilities within the dashboard to allow users to easily differentiate and locate WorkflowRun objects based on their source of initiation (CLI vs. VelaUX UI).
The text was updated successfully, but these errors were encountered: