Migrate from Kit to Taskfile

[alexec]

We should migrate the codebase to use Taskfile rather than Kit.

I've been using it on a recent project, and its a simple (YAML+Shell) popular (11k stars) task running. It can do almost everything that Kit can do, but has better documentation, and is easy to use.

I like it a lot.

I looked at other projects (e.g. Tilt) and found they tend to use complex DSLs.

cc. @agilgur5 @sarabala1979

[MasonM]

Interesting, I was just looking into Kit and ways of improving the dev environment. I have to say I'm really impressed with Kit. It's a solid piece of software that does its job well.

One Kit feature we use that Task lacks is concurrency control using mutexes. There's two mutexes in task.yaml, one called docker and one called build:

argo-workflows/tasks.yaml

Lines 21 to 32 in 7d7ebb1

	- name: install
	command: sh -c "make install PROFILE=$PROFILE"
	env:
	- PROFILE=minimal
	dependencies: go-deps
	watch: manifests
	mutex: docker
	- name: build-controller
	command: make ./dist/workflow-controller
	watch: cmd/workflow-controller config errors persist pkg util workflow
	dependencies: go-deps
	mutex: build

argo-workflows/tasks.yaml

Lines 56 to 62 in 7d7ebb1

	- name: build-argo
	command: make ./dist/argo
	dependencies: go-deps
	env:
	- STATIC_FILES=false
	watch: cmd/argo config errors persist pkg util server workflow
	mutex: build

argo-workflows/tasks.yaml

Lines 85 to 92 in 7d7ebb1

	- name: executor
	command: make argoexec-image
	watch: cmd/argoexec config errors pkg util workflow
	mutex: docker
	- name: example
	command: kubectl create -f examples/hello-world.yaml
	dependencies: install
	mutex: docker

I don't think the docker one is necessary, because none of the tasks with that mutex conflict with each other. The build one does look to be necessary because make ./dist/argo and make ./dist/workflow-controller will both try to regenerate pkg/apis/workflow/v1alpha1/generated.proto and that logic involves writing temporary files:

argo-workflows/Makefile

Lines 362 to 375 in 7d7ebb1

	pkg/apis/workflow/v1alpha1/generated.proto: $(GOPATH)/bin/go-to-protobuf $(PROTO_BINARIES) $(TYPES) $(GOPATH)/src/github.com/gogo/protobuf
	# These files are generated on a v3/ folder by the tool. Link them to the root folder
	[ -e ./v3 ] || ln -s . v3
	# Format proto files. Formatting changes generated code, so we do it here, rather that at lint time.
	# Why clang-format? Google uses it.
	find pkg/apiclient -name '*.proto'|xargs clang-format -i
	$(GOPATH)/bin/go-to-protobuf \
	--go-header-file=./hack/custom-boilerplate.go.txt \
	--packages=github.com/argoproj/argo-workflows/v3/pkg/apis/workflow/v1alpha1 \
	--apimachinery-packages=+k8s.io/apimachinery/pkg/util/intstr,+k8s.io/apimachinery/pkg/api/resource,k8s.io/apimachinery/pkg/runtime/schema,+k8s.io/apimachinery/pkg/runtime,k8s.io/apimachinery/pkg/apis/meta/v1,k8s.io/api/core/v1,k8s.io/api/policy/v1 \
	--proto-import $(GOPATH)/src
	# Delete the link
	[ -e ./v3 ] && rm -rf v3
	touch pkg/apis/workflow/v1alpha1/generated.proto

A workaround is to have make ./dist/argo be a dependency of make ./dist/workflow-controller or vice-versa.