From 2b23d640022551b8d9d9cfbcef9ebc35985f1531 Mon Sep 17 00:00:00 2001 From: Jeff Mitchell Date: Fri, 29 Jan 2016 10:36:37 -0500 Subject: [PATCH] changelog++ --- CHANGELOG.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index bd88070bab..ed6b7d16e6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -43,14 +43,18 @@ FEATURES: value is protected via any PGP key of the initiator's choosing or a one-time pad known only to the initiator (a suitable pad can be generated via the `-genotp` flag to the command. [GH-915] - * **DynamoDB HA Physical Backend**: There is now a new, community-supported - HA-enabled physical backend using Amazon DynamoDB. See the [configuration - documentation](https://vaultproject.io/docs/config/index.html) for details. - [GH-878] * **Keybase Support for PGP Encryption Keys**: You can now specify Keybase users when passing in PGP keys to the `init`, `rekey`, and `generate-root` CLI commands. Public keys for these users will be fetched automatically. [GH-901] + * **DynamoDB HA Physical Backend**: There is now a new, community-supported + HA-enabled physical backend using Amazon DynamoDB. See the [configuration + documentation](https://vaultproject.io/docs/config/index.html) for details. + [GH-878] + * **PostgreSQL Physical Backend**: There is now a new, community-supported + physical backend using PostgreSQL. See the [configuration + documentation](https://vaultproject.io/docs/config/index.html) for details. + [GH-945] * **STS Support in AWS Secret Backend**: You can now use the AWS secret backend to fetch STS tokens rather than IAM users. [GH-927]