From 90b691af84684a75e9fd114bb6848d541861f622 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Mon, 9 Nov 2026 14:48:49 -0500 Subject: [PATCH] docs(deployment): correct the QA leader-resolution note after scadaproj#43 Claude-Session: https://claude.ai/code/session_01GT67AEHd2Acv1YPwGfXEoV --- deployment.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/deployment.md b/deployment.md index a0245f4..467f62e 100644 --- a/deployment.md +++ b/deployment.md @@ -435,6 +435,11 @@ Three things worth carrying forward: false on the co-located VD03 box, where the workaround is to point every `BaseUrl` at `127.0.0.1` so resolution never matches and each chip falls back to the raw Akka address. On QA the leader chips resolve to real names (`node-a (vq03)`), so that workaround is **not** wanted here. + **Correction (2026-11-09, scadaproj#43):** before that fix the host match ran across the whole + application, so on QA a group that shares hosts with another (the ScadaBridge site group vs central) + could show the other group's leader (`central-a`). `LeaderResolver` now matches only within the + group's own members; an unmatched leader shows the raw Akka address. Two members of one group on the + same host still can't be told apart. ---