<#438 [Feature]UX for versions of a Workflow, Laun...
# flyte-github
a
#438 [Feature]UX for versions of a Workflow, Launch Plan and Task Issue created by kumare3 Motivation: Why do you think this is important? When a user registers a new version of a workflow, the current UX makes it extremely easy to launch an execution, but, it makes it hard to • discover: find workflows, tasks, launch plans and their versions as a chronology • debug: Check if a specific version was registered • Collate: executions collected by a specific version - might help the user finding which executions they are looking for • Document: Documentation - like code - is versioned and it might be useful to show the latest, but allow users to dive into previous versions Goal: What should the final outcome look like, ideally? UX should make it possible to find all registered versions of a workflow/task/launchplan, look for a specific SHA, look at the details of the configuration etc in the UI. User should be able to group all executions by a version User should be able to view the documentation of a workflow, launchplan and task Describe alternatives you've considered NA Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☐ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☑︎ FlyteConsole (UI) ☐ Other Comments This is lower priority than other things, but, will definitely help in creating a better debugging experience in Flyte. flyteorg/flyteconsole