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
It's not at all obvious from the documentation how I would convert from a known http api path to the path that I would use for a logical read method call or what I would set my prefixPathDepth to.
The text was updated successfully, but these errors were encountered:
with trial and error and the use of step debugging I was able to determine that my path should be secret/deployment/api and I should not specify any prefixPathDepth.
I think a source of confusion is that I was already using .../data/... in my paths for http api calls.
Please clarify in the readme/documentation how to determine the path and path depth. For example I can access my secrets with the following http call:
curl -s -H "X-Vault-Token: TOKEN" https://vault.example.com/v1/secret/data/deployment/api
which returns a json payload like:
It's not at all obvious from the documentation how I would convert from a known http api path to the path that I would use for a logical read method call or what I would set my prefixPathDepth to.
The text was updated successfully, but these errors were encountered: