include a --ca-file to helm3 plugin about drone-helm3 HOT 9 CLOSED

Amazing, Erin. I can't wait to test it. Thanks a lot! Great plugin, btw...

from drone-helm3.

Ooh, yeah that does seem more usable. Might be worthwhile to throw in a repo_certificate setting too.

from drone-helm3.

Hey, @ErinCall. I've just built the image and used it in my pipeline with the "repo_ca_certificate" param taking from a secret. I converted my cert to Base64 and everything worked flawlessly. That was, indeed, a more elegant approach.

from drone-helm3.

Sure, that should be no problem. Barring unforeseen mishaps, we can have it ready for you on Monday 🙂

The setting will probably be repo_ca_file, to avoid confusion with the Kube cluster’s CA.

from drone-helm3.

@alexismaior Ok, that setting is available in version 0.12.0. Let me know how it works for you!

from drone-helm3.

Worked perfectly, Erin. Thanks a lot. As the "ca-file" parameter expects a "file", I had to mount the volume to pass the ca.crt locally. I don't know if there is a better way to do that but worked.

from drone-helm3.

@ErinCall what would you think of taking the value from the ENV var and writing it to a file and then using that? it would allow for secrets to be injected in that way as well without mounting. :)

from drone-helm3.

@alexismaior I've just opened #76, which replaces the filepath setting with base64-encoded contents settings. Will it be a headache for you to switch your .drone.yml to match?

from drone-helm3.

@alexismaior yay, I'm glad it worked for you! That update is now live in version 0.13.0 :)

from drone-helm3.