Read specific vault key using vault path templating

[tsabados]

Is it possible to read a specific vault key using vault path templating?

Documentation suggests that it is possible like this:

key2: VAULT:/helm2/test/key2

where "key2" would be vault key under vault secret path "/helm2/test".

I have tested this with KV version v2 but the plugin seems to expect that there is a vault key named "value" under the secret path "/helm2/test/key2" specified in the path template.

I have already modified the plugin to use syntax like this:

key2: VAULT:/helm2/test;key2

but I am wondering if I am missing something here.

[Just-Insane]

Hello,

sorry for the late response on this.

As far as I am aware, Helm-Vault only supports reading keys/values either added by it or added using the same names as the keys it would add, which I think is just “value” as the key name.

I think it would be easy enough to add this functionality since all Vault interaction is done through a third-party client which should be able to read any key name, it just hadn’t been needed until now, and adds some complexity.

Development on this project has slowed unfortunately as I haven't had much time to tinker with Kubernetes/Vault lately, but if you are able to open a PR I can get it reviewed and merged.