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
{{ message }}
This repository has been archived by the owner on Sep 30, 2019. It is now read-only.
Hello.
I use scala-vault 0.4.1 and it doesn't work with vault 0.10.4.
My code:
val config = VaultConfig(WSClient(new URL("http://localhost:8200")), "root")
val secrets = Secrets(config, "secret")
val response1 = secrets.set("some_secret", "some_key", "some_value")
println(response1.attemptRun)
val response = secrets.getAll("some_secret")
println(response.attemptRun)
Results:
Ok(Fail(Received failure response from server: 404
{"request_id":"4b8b8334-1f9e-8b5e-5970-58f632831756","lease_id":"","renewable":false,"lease_duration":0,"data":null,"wrap_info":null,"warnings":["Invalid path for a versioned K/V secrets engine. See the API docs for the appropriate API endpoints to use. If using the Vault CLI, use 'vault kv put' for this operation."],"auth":null}))
Ok(Fail(Received failure response from server: 404
{"request_id":"2f22cc0f-3ec1-7f24-0d01-e9b74b57b74b","lease_id":"","renewable":false,"lease_duration":0,"data":null,"wrap_info":null,"warnings":["Invalid path for a versioned K/V secrets engine. See the API docs for the appropriate API endpoints to use. If using the Vault CLI, use 'vault kv get' for this operation."],"auth":null}))
With vault 0.6.2 everything works correctly.
I did some debug with simple ruby application (vault doesn't show API calls) and looks like API has been changed:
When I'll try to create secret with official client i get:
Hello.
I use scala-vault 0.4.1 and it doesn't work with vault 0.10.4.
My code:
Results:
With vault 0.6.2 everything works correctly.
I did some debug with simple ruby application (vault doesn't show API calls) and looks like API has been changed:
When I'll try to create secret with official client i get:
With scala-vault:
The text was updated successfully, but these errors were encountered: