Releases: Mcfloy/vault-credentials
Releases · Mcfloy/vault-credentials
Kubernetes: Breaking change on the name path and token path.
The Kubernetes workflow is refactored in order to allow a custom solution that doesn't respect the Vault official documentation.
To set a path you must use K8S_SERVICE_ACCOUNT_TOKEN
environment variable, and VAULT_K8S_AUTH_PATH
is now optional.
v0.4: Asynchronous retrieval
The init method is now asynchronous, as previously we would use the blocking reqwest's client and it would crash when using a Tokio runtime.
With this release we can use the vault-credentials crate inside a tokio runtime.
v0.3: Namespace
- Can authenticate to Vault using a namespace.
v0.2: Simple authentication
- Can authenticate using a vault token
- Can authenticate using a vault role id and secret id
- Can authenticate using a userpass or ldap
- Can authenticate using Kubernetes