From 2a2c348e0bd526cbaf4d28a27de793ec2c0a960c Mon Sep 17 00:00:00 2001 From: Chris Hoffman Date: Mon, 9 Apr 2018 09:40:51 -0400 Subject: [PATCH] changelog++ --- CHANGELOG.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5c14c35419..20cf28495f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -20,6 +20,10 @@ DEPRECATIONS/CHANGES: default. Existing configurations will continue to work as they do now; however, the next time a configuration is written `case_sensitive_names` will need to be explicitly set to `true`. + * TTL handling within core: All lease TTL handling has been centralized within + the core of Vault to ensure consistency across all backends. Since this was + previously delegated to individual backends, there may be some slight + differences in TTLs generated from some backends. FEATURES: @@ -41,8 +45,8 @@ FEATURES: Vault, invalidating the old credentials and ensuring only Vault knows the actual valid values. * Azure Authentication Plugin: There is now a plugin (pulled in to Vault) that - allows authenticating Azure machines to Vault using their Azure-provided - credentials. See the [plugin + allows authenticating Azure machines to Vault using Azure's Managed Service + Identity credentials. See the [plugin repository](https://github.com/hashicorp/vault-plugin-auth-azure) for more information. * GCP Secrets Plugin: There is now a plugin (pulled in to Vault) that allows