Redesign: Auth and Secrets usage of Endpoints

[kenjones-cisco]

The pattern of defining APIs/Endpoints in a file works well for fixed Endpoints. But for the different Secret backends and the Auth Backends, the actual Endpoint is going to vary based on how those are mounted.

For example, if the operator of the Vault mounts a consul type secret backend to consul-prd, then attempting to use the Consul Endpoints located at the fixed location /v1/consul/* will result in many 404 type errors.

As a result the pattern for doing Endpoints will need to be redesigned.

[kenjones-cisco]

Secret Backends

Mounting consul:

-d '{"type":"consul"}' /sys/mounts/consul-prd

APIs available at /v1/consul-prd/* instead of default /v1/consul/*

Auth Backends

Enabling app-id:

-d '{"type":"app-id"}' /sys/auth/local-appid

APIs available at /v1/auth/local-appid/* instead of default /v1/auth/app-id/*