You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to be very similar to the #174 issue with List/Read being mapped to the same method in the OpenAPI spec. The full solution will need to be implemented in hashicorp/vault and/or hashicorp/vault-plugin-secrets-kv but in the meantime your workaround should work. Alternatively, substituting the call with client.Read(ctx, ...) should work as well.
When trying to retrieve a key-value from the secrets engine, I get back a not found for a key that does exist:
(I am using the v1 API for legacy reasons)
Expected Behavior
I expect to be able to read the secret stored with the given key.
Current Behavior
I get back a 404.
Failure Information
Please include the version of Vault binary and the version of
vault-client-go
you're using.vault-client-go: 0.3.3
vault: 1.13.4
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
client.Secrets.KvV1Read
call...
Additional Information
As a workaround that I used a custom request callback function:
With this set as a request callback the request goes through.
The text was updated successfully, but these errors were encountered: