Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify relationship between http api path and read path #232

Open
madcap opened this issue Nov 10, 2020 · 1 comment
Open

clarify relationship between http api path and read path #232

madcap opened this issue Nov 10, 2020 · 1 comment

Comments

@madcap
Copy link

madcap commented Nov 10, 2020

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:

{
  "request_id":"some uuid",
  "lease_id":"",
  "renewable":false,
  "lease_duration":0,
  "data":{
    "data":{
      "key1":"value1"
      ...

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.

@madcap
Copy link
Author

madcap commented Nov 10, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant