3ce9615992
For situations where you want the Vault agent to handle one or more templates but do not require the acquired credentials elsewhere. Modify the logic in SyncServer so that if there are no sinks, ignore any new credentials. Since SyncServer is responsible for shutting down the agent, make sure it still properly shuts down in this new situation. Solves #7988 |
||
---|---|---|
.. | ||
auth | ||
cache | ||
config | ||
sink | ||
template | ||
README.md | ||
alicloud_end_to_end_test.go | ||
approle_end_to_end_test.go | ||
aws_end_to_end_test.go | ||
cache_end_to_end_test.go | ||
cert_with_name_end_to_end_test.go | ||
cert_with_no_name_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: