Initial thoughts: have it proxy the Monzo API directly without much validation on our end.
Thinking we just have a /proxy/* handler, which proxying the API, but returning the results in Vault Secret format.
Thinking we could also have a /proxy/raw/* handler, again proxying the API, but returning the results directly. We'd still have auth handled via X-Vault-Token headers (or Authorization: Bearer if you like). This could allow for existing Monzo API clients to talk directly to the Vault plugin without changes... but might not work.
Initial thoughts: have it proxy the Monzo API directly without much validation on our end.
Thinking we just have a
/proxy/*
handler, which proxying the API, but returning the results in Vault Secret format.Thinking we could also have a
/proxy/raw/*
handler, again proxying the API, but returning the results directly. We'd still have auth handled viaX-Vault-Token
headers (orAuthorization: Bearer
if you like). This could allow for existing Monzo API clients to talk directly to the Vault plugin without changes... but might not work.