You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bf68e0b
Browse filesBrowse the repository at this point in the historyBrowse files
fix(providers): serialize refresh configuration to reserve keys atomically
Refresh configuration validated key availability and persisted the
reservation as separate steps. Two concurrent configures of providers
attached to the same sandbox could each pass validation before either
persisted, then both reserve the same primary or additional output key,
leaving conflicting unusable refreshes (CWE-362).
Hold the process-wide sandbox sync guard across the reserve-and-persist
sequence — the same guard sandbox create/attach and profile changes take
— so configurations and sandbox mutations that share the credential-key
namespace are serialized. Add a concurrent-configure regression test
asserting exactly one configuration reserves the key.
Signed-off-by: Russell Bryant <[email protected]>
0 commit comments