stacklok / toolhive / 23979882227

push

github

Route OIDCConfigHash through StatusManager in VirtualMCPServer (#4539)

handleOIDCConfig wrote OIDCConfigHash directly via r.Status().Update()
while every other status field used the batched StatusManager. This
mixed-write pattern could produce spurious 409 Conflict errors when the
original vmcp object's resourceVersion became stale after earlier
applyStatusUpdates calls in the same reconciliation.

Add SetOIDCConfigHash to the StatusManager interface and route both the
set and clear paths through it, eliminating all direct VirtualMCPServer
status writes from handleOIDCConfig.

Fixes #4504

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

8 of 18 new or added lines in 3 files covered. (44.44%)

54671 of 83852 relevant lines covered (65.2%)

63.31 hits per line