Delete go/cmd/automation_{client,server}

[ajm188]

Signed-off-by: Andrew Mason amason@slack-corp.com

Description

Just a git rm -rf ./go/cmd/automation_{client,server}. I've never actually deleted a binary from vitess so I'm not sure if this is the right process (i.e. should we "deprecate" the binary by having it print a warning whenever you try to run it?)

Related Issue(s)

#9222

Checklist

• Should this PR be backported? no
• Tests were added or are not required n/a
• Documentation was added or is not required n/a

Deployment Notes

[deepthi]

I've never actually deleted a binary from vitess so I'm not sure if this is the right process (i.e. should we "deprecate" the binary by having it print a warning whenever you try to run it?)

In this case I think we are sure that these binaries are defunct.
For something like vtctlclient we will go through a proper deprecation cycle.

Why not delete the go/vt/automation package along with cmd/automation_*?

[ajm188]

Why not delete the go/vt/automation package along with cmd/automation_*?

It's used in a few other places, namely vtworker (which is also being deleted but will be a much larger diff):

❯ go list -f '{{ .ImportPath }}:{{ .Deps }}' ./... | grep 'go/vt/automation' | cut -d ':' -f1
vitess.io/vitess/go/cmd/automation_server
vitess.io/vitess/go/cmd/vtcombo
vitess.io/vitess/go/cmd/vtctld
vitess.io/vitess/go/vt/automation
vitess.io/vitess/go/vt/vtctld
vitess.io/vitess/go/vt/workflow/resharding
vitess.io/vitess/go/vt/workflow/reshardingworkflowgen