Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Vault Transit support #1166

Closed
danlsgiga opened this issue Jan 9, 2019 · 2 comments
Closed

[FEATURE] Vault Transit support #1166

danlsgiga opened this issue Jan 9, 2019 · 2 comments

Comments

@danlsgiga
Copy link

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!

@danlsgiga danlsgiga changed the title [FEATURE]: Vault Transit support [FEATURE] Vault Transit support Jan 9, 2019
@thevilledev
Copy link
Contributor

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?

@danlsgiga
Copy link
Author

Yeah, since this is a really old issue I'm considering my use case at the time and it does solve it.
closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants