ae79afdd26
Uses a bufconn listener between consul-template and vault-agent when caching is enabled and either templates or a listener is defined. This means no listeners need to be defined in vault-agent for just templating. Always routes consul-template through the vault-agent cache (instead of only when persistent cache is enabled). Uses a local transportDialer interface in config.Cache{}. Co-authored-by: Tom Proctor <tomhjp@users.noreply.github.com> Co-authored-by: Ben Ash <32777270+benashz@users.noreply.github.com> |
||
---|---|---|
.. | ||
auth | ||
cache | ||
config | ||
sink | ||
template | ||
winsvc | ||
README.md | ||
alicloud_end_to_end_test.go | ||
approle_end_to_end_test.go | ||
auto_auth_preload_token_end_to_end_test.go | ||
aws_end_to_end_test.go | ||
cache_end_to_end_test.go | ||
cert_end_to_end_test.go | ||
cf_end_to_end_test.go | ||
doc.go | ||
jwt_end_to_end_test.go | ||
testing.go |
README.md
Vault Agent
Vault Agent is a client daemon that provides Auth-Auth, Caching, and Template features.
Vault Agent provides a number of different helper features, specifically addressing the following challenges:
- Automatic authentication
- Secure delivery/storage of tokens
- Lifecycle management of these tokens (renewal & re-authentication)
See the usage documentation on the Vault website here: