Type '/' to Search

»Overview

This page contains the list of deprecations and important or breaking changes for Vault 1.6.0 compared to 1.5. Please read it carefully.

»Go Version

Vault 1.6.0 is built with Go 1.15. Please review the Go Release Notes for full details. A few items of particular note:

  • Go 1.15 has dropped support for 32-bit binaries on macOS, iOS, iPadOS, watchOS, and tvOS, and Vault is no longer issuing darwin_386 binaries
  • Go 1.15 no longer treats the CommonName field on X.509 certificates as a host name. X.509 certificates should be validated and potentially regenerated before upgrading if they do not have Subject Alternative Names.

»Transform Secrets Engine Storage Upgrade

The Transform Secrets Engine (Enterprise only) will automatically upgrade the storage of its configuration in order to accommodate the new transformation type oriented configuration API. Secondaries will receive the modifications via replication.

»Database Engine Interface Upgrade

The Database Engine has changed the underlying interface between Vault and each database implementation. This change allows use of password policies within the Database engine. The API for the Database Engine has not changed, only the underlying interface between Vault and the database plugins. All built-in database plugins (as well as the Oracle plugin) have been upgraded to the new interface so no user actions are needed. Vault will continue to recognize existing custom database plugins but the old interface should be considered deprecated and may be removed in a future release. See our upgrade guide for custom databases for more information on upgrading custom database plugins.

»Known Issues

Due to the known issue, Transform Secrets Engine users are recommended to upgrade to version 1.6.4.

»Transform Storage Upgrades Fixed

The Transform Secrets Engine storage upgrade introduced in 1.6.0 introduced malformed configuration for transformations configured earlier than 1.6.0, resulting in an error using these transformations if Vault is restarted after the upgrade. This issue exists on Vault 1.6.0 through 1.6.3, and is fixed in Vault 1.6.4 and 1.7.0. Transformations configured on 1.6.0 or higher are unaffected.