Update version of KV secrets engine plugin

[maxb]

Only change is to set the TakesArbitraryInput metadata on the KV v1
endpoint, which we need to fix hashicorp/vault-client-go#201.

[averche]

Hi @maxb! I believe we would need to release each affected plugin first and link against the released version. I'll try to take care of it this week :)

In the meantime, If you want to regenerate the latest openapi.json for vault-client-go / vault-client-dotnet, feel free to just use the replace directive in your local vault's go.mod (or go.work):

replace github.com/hashicorp/vault-plugin-secrets-kv => /path/to/your/vault-plugin-secrets-kv

Since the two client libraries are still in BETA and there is no established CI workflow, the openapi.json in the libraries does not need to strictly match the one generated in the main branch of Vault.

[maxb]

I believe we would need to release each affected plugin first and link against the released version.

Right, that would be one way to do it. Really it comes down to HashiCorp internal policy and how you want to manage such things:

• You could decide that it's only acceptable to use released tagged versions of plugins in the Vault main branch

• Or you could decide pseudo-versions are fine in the middle of the Vault development cycle, and you'll use the batch of plugin releases that usually seem to occur when getting ready to fork a new Vault release branch to set any pseudo-versions used during development back to real tags

Either way, if you're happy for vault-client-go/dotnet to be updated with locally generated OpenAPI specs based on future plugin versions yet to be merged, there's no hurry to get these versions increased in the short term.

[maxb]

I'll try to take care of it this week :)

Maybe hold off a little longer - I'm now up to 4 open PRs against the KV plugin :-) (Not all OpenAPI-related, I hasten to add.)

[maxb]

Closed, as it looks like we'll not be using this diff as is.