CHANGELOG.md

2.0.1

SECURITY FIXES

• Resolve https://rustsec.org/advisories/RUSTSEC-2021-0020 via #45.

FEATURES

• Update tested Vault releases to include latest versions.

• Migrate CI testing to Github actions.

• Add support for custoim secret types (#44).

  The new secret types allow for managing arbitrary data in Vault as long as the data is serializable!

BREAKING CHANGES

• Rust 1.42 is now required

1.1.0

FEATURES

• escape now escapes '"', allowing JSON to be saved into a secret.
• Update gate tests to use released Vault 1.4.0.

1.0.0

FEATURES

• AppRole auth backend support added: https://www.vaultproject.io/docs/auth/approle.html.
• VaultResponse
• Added request_id field. Added in vault 0.6.1: hashicorp/vault#1650.

BREAKING CHANGES

• VaultClient
• data is now Option<VaultResponse<T>>. The standard function, VaultClient::new, for constructing a VaultClient makes a call to the auth/token/lookup-self endpoint to populate additional information about the token. However, for limited use tokens, you will not want to perform this lookup. As a result, the VaultClient.data has now been made an Option.
• cubbyhole/response endpoint is deprecated in vault 0.6.2 and has been replaced by sys/wrapping/unwrap. The function get_cubbyhole_response() has been renamed to get_unwrapped_response(). More details: hashicorp/vault#1927.