You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really nice to have support for Vault Transit encryption so we can manage secrets directly in git and consul-template would only decrypt it using the Transit endpoint at runtime.
It would also provide a performance boost on the Vault servers for static secrets since consul-template won't need to watch for changes.
IMO, it would be a game changing feature!
The text was updated successfully, but these errors were encountered:
danlsgiga
changed the title
[FEATURE]: Vault Transit support
[FEATURE] Vault Transit support
Jan 9, 2019
Echoing what was stated in #1871 since this is quite an old issue. consul-template nowadays has a built-in secret template function which enables a generic read/write interface to any Vault backend. This includes the transit backend, so any GET/POST call towards the backend can already be done with consul-template.
@danlsgiga does this match what you were looking for?
It would be really nice to have support for
Vault Transit
encryption so we can manage secrets directly in git and consul-template would only decrypt it using the Transit endpoint at runtime.It would also provide a performance boost on the Vault servers for static secrets since consul-template won't need to watch for changes.
IMO, it would be a game changing feature!
The text was updated successfully, but these errors were encountered: