-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Unified workflows list UI and API #11121
Conversation
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
For workflow deletion, we need to delete workflow in K8s cluster and in the DB. Here's what I propose we should do:
For the backend, we can choose either of the following:
Any thoughts? @jessesuen @sarabala1979 |
There should also be a setting (e.g. environment variable) to enable/disable the popup. |
Signed-off-by: Yuan Tang <[email protected]>
I like it. if the workflow is in one place(either k8s/DB), just delete it Are you going to show the icon in the workflow list |
Discussed with Bala, for the backend we'll use this approach:
Right now it's text "true/false" in the column. The icon doesn't look good in the column and the meaning of the icon is not intuitive. |
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Agree with you that global var UI solution isn't ideal, but for now works and shouldn't have side effects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some back-links to fixes for issues here for posterity
initialPodName={podName} | ||
nodeId={parsedSidePanel.nodeId} | ||
container={parsedSidePanel.container} | ||
archived={isArchivedWorkflow(workflow)} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this appears to cause a subtle regression for logs for Workflows that are both live and archived (e.g. ones that have not TTL'd yet): #12948 (comment)
Fixes #10781.