-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Vtctld Workflow command: minor fixes #7008
Conversation
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
@PrismaPhonic, there is a breaking change: you will need to call wr.ListActiveWorkflows() instead of wr.ListAllWorkflows() in PSDB Sharding Workflows when you use a Vitess distro after this is merged. Also please check that any other change in this PR will not impact you. |
Wouldn't this result in also revealing potentially a large number of FROZEN workflows that never got cleaned up? |
Yes, it will be useful to get users to cleanup their frozen workflows as a best practice. Users have also begun to use Workflow Delete to cleanup, so in general we should not have a lot of FROZEN workflows in any case. |
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
Workflow ListAll now includes stopped workflows. It was implemented to only give the active workflows as per PSDB's requirement. However this is confusing for regular users who don't see a created workflow if streams are in Stopped state.
Also improved output for ListAll: in particular, when there are no workflows an explicit message is provided instead of nothing
If an invalid workflow name is provided Workflow Show now errors out (earlier an inconsistent output was shown)
Signed-off-by: Rohit Nayak rohit@planetscale.com