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.
16 lines
566 B
Markdown
16 lines
566 B
Markdown
# Drone plugin for Helm 3
|
|
|
|
TODO:
|
|
|
|
* [x] Make a `.drone.yml` that's sufficient for building an image
|
|
* [x] Make a `Dockerfile` that's sufficient for launching the built image
|
|
* [x] Make `cmd/drone-helm/main.go` actually invoke `helm`
|
|
* [x] Make `golint` part of the build process (and make it pass)
|
|
* [x] Implement debug output
|
|
* [x] Flesh out `helm upgrade` until it's capable of working
|
|
* [ ] Implement config settings for `upgrade`
|
|
* [ ] Implement `helm lint`
|
|
* [ ] Implement `helm delete`
|
|
* [ ] EKS support
|
|
* [ ] Change `.drone.yml` to use a real docker registry
|