mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2025-11-28 22:21:30 +01:00
Code Issues Projects Releases Wiki Activity

make correction to known issue to include roles created prior to 1.15.0 (#30448)

Browse Source 
* make correction to known issue to include roles created prior to 1.15.x

* make wording more clear

* reword
This commit is contained in:
Ellie 2025-04-29 19:39:46 -05:00 committed by GitHub
parent 485ccbc5da
commit 70c0a7af97
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
website/content/partials/known-issues/database-static-role-premature-rotations.mdx
View File

@ -1,24 +1,16 @@
### Database static role rotations on upgrade ((#db-static-role-rotations))
#### Affected Upgrade Path
* This issue only occurs when upgrading from the following initial versions to the following target versions:
### Affected Roles
Any database static role that was created prior to Vault 1.15.0 will be affected upon upgrading to the following Vault versions:
Initial Versions (any version prior to 1.15.0):
- 1.14.x
- 1.13.x
- and earlier
Target Versions:
### Affected Versions:
- 1.19.0, 1.19.1, 1.19.2
- 1.18.5, 1.18.6, 1.18.7, 1.18.8
- 1.17.12, 1.17.13, 1.17.14, 1.17.15
- 1.16.16, 1.16.17, 1.16.18, 1.16.19
#### Issue
Vault automatically rotates existing static roles tied to Database
credentials once when upgrading to an affected target version from an
affected initial version. After the one-time rotation, the static roles behave as expected.
### Issue
Vault will automatically rotate static database credentials once, for all roles created prior to 1.15.0, when upgrading to affected versions.
After the one-time rotation, the static roles behave as expected.
#### Workaround
If you rely on Database static roles and are currently on a version prior to 1.15.0,
avoid upgrading directly to the target versions listed above.