Vault KV v2: cannot access subkeys/ path via consul-template

[ryansammonaiven]

Currently, the code that shims data/ into Vault KV v2 paths only checks if the path starts with data/ or metadata/. (code)

This effectively means that only these paths are accessible within Vault KV v2 secrets engines.

For example, attempting to access a path starting with subkeys/ (Vault API Docs) will result in the shim transforming the path to data/subkeys/..., missing the desired endpoint.

The code that shims data/ into Vault KV v2 paths needs to check for every possible valid prefix before deciding to shim in data/.