flyteorg / flyte

Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
https://flyte.org
Apache License 2.0
5.47k stars 584 forks source link

[UI Feature] Show all launchplan associated with a workflow in workflow details page #3480

Open pradithya opened 2 years ago

pradithya commented 2 years ago

Motivation: Why do you think this is important?

It's currently not possible from flyte console to see all available launchplan associated with a workflow.

Goal: What should the final outcome look like, ideally?

Launch plan is one resource that doesn't have much visibility in flyte console. Having no visibility of launch plan is not critical as long as users trigger a workflow via deliberate action (either using flyte remote or create execution from UI itself), however it become inconvenience when users have scheduled workflow.
With scheduled workflow users set the schedule and launch plan's inputs in advance. There also can be multiple launch plan for a given workflow with different schedule and different inputs. And since the execution happens later than the launch plan creation itself, it is important for the users to be able to visually validate all launch plan that's associated with a workflow, their configuration (i.e. schedule, inputs) and whether they are active to ensure that their scheduled launch plans are ready.

Propose: Link/Inline OR Additional context

Ideally, launchplan information is available within workflow details page (i.e /projects/project/domains/domain/workflows/workflow).
The information can be served as a table similar to the list of execution and the content is similar to what flytectl get launchplan command provides e.g.

 --------- ------------------------------------------------ ------ ------- ------------------------------------------- -------------- ---------
| VERSION | NAME                                           | TYPE | STATE | SCHEDULE                                  | INPUTS       | OUTPUTS |
 --------- ------------------------------------------------ ------ ------- ------------------------------------------- -------------- ---------
| aa8d820 | awesome_workflow.workflows.launchplan.schedule |      |       | map[cronSchedule:map[schedule:0 10 * * 1] | kickoff_time | o0      |
|         |                                                |      |       | kickoffTimeInputArg:kickoff_time]         |              |         |
 --------- ------------------------------------------------ ------ ------- ------------------------------------------- -------------- ---------
| fe791e5 | awesome_workflow.workflows.launchplan.schedule |      |       | map[cronSchedule:map[schedule:0 10 * * 1] | a            | o0      |
|         |                                                |      |       | kickoffTimeInputArg:kickoff_time]         | b            |         |
|         |                                                |      |       |                                           | kickoff_time |         |
 --------- ------------------------------------------------ ------ ------- ------------------------------------------- -------------- ---------

and clicking one of the launch plan will lead to opening launchplan details page. (related to flyteorg/flyteconsole#407)

Are you sure this issue hasn't been raised already?

Have you read the Code of Conduct?

kumare3 commented 2 years ago

Cc @jsonporter

pradithya commented 2 years ago

@jsonporter @kumare3 The UX could be as follow:

Launch Plan UI_UX

kumare3 commented 2 years ago

Cc @jsonporter

github-actions[bot] commented 9 months ago

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏