I'd disagree with changing the default, let me come up with a different solution

casz, jacobtruman is absolutely right, I would like to not have to change any existing workflow scripts since many of them are outside of our control. I would argue that the default has already been changed with 2.3.0 and should be set to 1 to match the previous behavior, but I can understand completely if you don't want to do it that way. I would quite happy with a solution that let me set the default version system wide (perhaps in the global configuration options?) so that individual teams/users don't have to update their scripts to have it continue working with v1 engine versions.

Thanks!

You work fast casz, this is exactly what I was looking for, thanks! Any idea on timeline for the next release?

v2.3.1 should be in the update center shortly

Tried it out this morning, and works great. Thanks for the quick turnaround on this!

I am quite concerned that when enabling v2 in configuration (at any level), if K/V engine v2 is not enabled in Vault after upgrading from v1, not a single explicit error shows up in both Jenkins & Vault logs, secret is retrieved with no data and envVars are not set:

No such property: testing for class: groovy.lang.Binding

misterz I know for a fact it will throw an error.

Could you share more information on what you're trying to attempt? Since without further details I have no chance of helping you.

1) Updated Hashicorp Vault from 0.9.6 to 1.0+

2) Updated plugin from 2.1.1 to 2.3.1 (bumps Java vault driver 2.0.0 to 4.0.0)

Result: nothing was working anymore without an explicit error message and engine v2 was set by default globally (Jenkins configured with CasC 1.27)

Possible fixes I used:

• explicitly set engine v1 usage in CasC

• upgrade existing version 1 kv store to version 2 kv store with CLI command
   vault kv enable-versioning secret/

I don't know if there is a way to have an explicit error when trying to use API v2 on a K/V engine v1, but it might save users from troubles

misterz, this sounds like a new problem unrelated to the actual problem fixed in this one, does that sound right? I could see how the summary might lead you to think it's the same issue, but the real problem for us is that the default engine version was 2 for everything instead of 1.

Yes, maybe I should create a new issue, my intent was to discuss that setting a default engine version does not prevent issues or show explicit errors when trying to use engine v2 on v1 (or v1 on v2)