13c663e906
This change revealed more about how the system needs to work, so there
are some supporting changes:
* helm.upgrade and helm.help are now vars rather than raw functions.
This allows unit tests to target the "which step should we run"
logic directly by comparing function pointers, rather than having to
configure/prepare a fully-valid Plan and then infer the logic’s
correctness based on the Plan’s state.
* configuration that's specific to kubeconfig initialization is now part
of the InitKube struct rather than run.Config, since other steps
shouldn’t need access to those settings (particularly the secrets).
* Step.Execute now receives a run.Config so it can log debug output.
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 - Make
golintpart of the build process (and make it pass) - Implement debug output
- Flesh out
helm upgradeuntil it's capable of working - Implement config settings for
upgrade - Implement
helm lint - Implement
helm delete - EKS support
- Change
.drone.ymlto use a real docker registry