suffix /data to secret path only when using v2 KV secret engine

[c35sys]

Try fo fix #41

[dirtycajunrice]

Interesting. So the /data path is not used with kv-v1 ?

[c35sys]

Interesting. So the /data path is not used with kv-v1 ?

No, it is new since v2.

Here are the curl requests I made:

v1

v1 request:

curl --header "X-Vault-Token: xxx" \
    https://xxx:8200/v1/testkv/teamA/hello-service | jq .

v1 response:

{
  "request_id": "05fa4c93-05c6-d616-591b-7292a584ee4e",
  "lease_id": "",
  "renewable": false,
  "lease_duration": 2764800,
  "data": {
    "private-images": "{ \"auths\": {\"registry.example.com\":{\"username\":\"foo\",\"password\":\"bar\",\"email\":\"foo@example.com\"}}}",
    "serviceBapiKey": "foo-123",
    "serviceCapiKey": "bar-456"
  },
  "wrap_info": null,
  "warnings": null,
  "auth": null
}

I changed testkv engine from v1 to v2, then I had to append /data

v2

v2 request:

curl --header "X-Vault-Token: xxx" \
    https://xxx:8200/v1/testkv/data/teamA/hello-service | jq .

v2 response:

{
  "request_id": "0b1797d5-e27a-f367-a5b9-90c9e2ae75af",
  "lease_id": "",
  "renewable": false,
  "lease_duration": 0,
  "data": {
    "data": {
      "private-images": "{ \"auths\": {\"registry.example.com\":{\"username\":\"foo\",\"password\":\"bar\",\"email\":\"foo@example.com\"}}}",
      "serviceBapiKey": "foo-123",
      "serviceCapiKey": "bar-456"
    },
    "metadata": {
      "created_time": "2020-09-30T07:24:05.859896046Z",
      "deletion_time": "",
      "destroyed": false,
      "version": 1
    }
  },
  "wrap_info": null,
  "warnings": null,
  "auth": null
}

[mcavoyk]

LGTM. Thanks for PR