990d1856d8
The recommended way to test code that uses exec.Cmd involves setting up a real exec.Cmd that invokes `go test` with additional arguments that fire off a specially-constructed test that behaves the way the mocked- out script would be expected to do. It's a sensible way to test exec.Cmd itself, but for code that merely invokes it, I think it makes more sense to use actual mocks.
Drone plugin for Helm 3
TODO:
- Make a
.drone.ymlthat's sufficient for building an image - Make a
Dockerfilethat's sufficient for launching the built image - Make
cmd/drone-helm/main.goactually invokehelm - Change
.drone.ymlto use a real docker registry