keyvault client
: fix concurrent write/read to keyvault cache
#28330
+13
−34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Description
The
keysmith
locker andlock
locker map cannot ensure that all operations on the cache map are properly locked. In Go's standardmap
structure, you cannot lock a specifickey
and operate on it separately; the entire map must be locked. This PR removes thelock
map, as the provider runs in client mode and does not require high concurrency. Therefore, a global lock is sufficient for performance (and we use RWLocker to mitigate the impact).Testing
The failed cases are not related to this change:
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_keyvault_xx
- Fix crash during concurrent read/write to cache map. [fatal error: concurrent map read and map write (succeeded on retrying apply) #28274]This is a (please select all that apply):
Related Issue(s)
Fixes #28274