dentaku/woodpecker-helm3
1
0
Fork 0
Code Pull requests Releases Activity
Plugin for woodpecker to deploy helm charts using helm3
10 commits 1 branch 0 tags 3.2 MiB
Go 98.8%
Smarty 0.9%
Dockerfile 0.3%
Find a file
Erin Call 4cbb4922fb
Implement the debug flag and help command 
I'm vacillating about the choice to have separate Config structs in the
`helm` and `run` packages. I can't tell whether it's "good separation of
concerns" or "cumbersome and over-engineered." It seems appropriate at
the moment, though.
2019-12-10 15:33:50 -08:00
cmd/drone-helm Replicate most of drone-helm's config 2019-12-09 09:58:42 -08:00
internal Implement the debug flag and help command 2019-12-10 15:33:50 -08:00
.drone.yml Run golint during drone builds 2019-12-09 15:27:56 -08:00
.gitignore Make it so 2019-11-21 11:35:50 -08:00
Dockerfile Initial config for building the plugin itself 2019-12-03 09:50:15 -08:00
go.mod Run golint during drone builds 2019-12-09 15:27:56 -08:00
go.sum Run golint during drone builds 2019-12-09 15:27:56 -08:00
LICENSE Make it so 2019-11-21 11:35:50 -08:00
README.md Implement the debug flag and help command 2019-12-10 15:33:50 -08:00

README.md

Drone plugin for Helm 3

TODO:

  • Make a .drone.yml that's sufficient for building an image
  • Make a Dockerfile that's sufficient for launching the built image
  • Make cmd/drone-helm/main.go actually invoke helm
  • Make golint part of the build process (and make it pass)
  • Implement debug output
  • 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