●Change8

Migrating to Vault v1.19.1

Version v1.19.1 introduces 1 breaking change. This guide details how to update your code.

Released: 4/4/2025

1
Breaking Changes
1
Migration Steps
14
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

auth/azureauth/gcpsecrets/azuresecrets/gcpsecrets/openldapsys/internal/counters/activityhashicorp/raftauth/awsauth/ldapaws/secretscore (enterprise)identitysecrets/dbsecrets/pki

Breaking Changes

●Issue #1

The Azure auth plugin now requires `resource_group_name`, `vm_name`, and `vmss_name` to match token claims during login due to an update to plugin v0.20.2.

✓Solution

Ensure that the claims presented during Azure authentication match the required resource group name, VM name, and VMSS name.

Migration Steps

  1. 1
    If using the Azure auth method, verify that the claims presented during login include `resource_group_name`, `vm_name`, and `vmss_name`.

Release Summary

Vault Enterprise 1.19.1 is an LTS release focused on stability, including numerous bug fixes across various auth and secret engines, particularly addressing panics on performance standby nodes. It also updates several underlying plugins to newer versions.

Need More Details?

View the full release notes and all changes for Vault v1.19.1.

View Full Changelog