Hashicorp Vault adds FDB as a storage option

wwilson · July 25, 2018, 10:29pm

hashicorp/vault/blob/master/CHANGELOG.md

## 0.10.4 (July 25th, 2018)

SECURITY:

 * Control Groups: The associated Identity entity with a request was not being
   properly persisted. As a result, the same authorizer could provide more than
   one authorization.

DEPRECATIONS/CHANGES:

 * Revocations of dynamic secrets leases are now queued/asynchronous rather
   than synchronous. This allows Vault to take responsibility for revocation
   even if the initial attempt fails. The previous synchronous behavior can be
   attained via the `-sync` CLI flag or `sync` API parameter. When in
   synchronous mode, if the operation results in failure it is up to the user
   to retry.
 * CLI Retries: The CLI will no longer retry commands on 5xx errors. This was a
   source of confusion to users as to why Vault would "hang" before returning a
   5xx error. The Go API client still defaults to two retries.
 * Identity Entity Alias metadata: You can no longer manually set metadata on

This file has been truncated. show original

Anybody know more about this?

bbc · July 26, 2018, 4:38am

Awesome news! The original PR is an interesting read and has a few details. There is some description of how the data is laid out, etc.

We would love to hear how it works for people in the community!