novox/mesh-controller
Archived
9
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

A mesh seat's holder elsewhere answers before this machine's own provider (hq issue 258) #59

Merged
mesh-admin merged 2 commits from fix/a-mesh-seat-answers-before-the-machines-own into main 2026-10-05 19:14:25 +00:00
Conversation 1 Commits 2 Files Changed 3
+110 -10
2 Commits
Author SHA1 Message Date
jochen ce86d09d22 A mesh seat's holder elsewhere answers before this machine's own provider (issue 258) 
A mesh-wide provision a machine could answer itself was bound to the local provider, with the
seat's holder and any pin consulted only for a provider on another machine. With every machine
still running its own resolver, each bound its resolver configuration to itself while the mesh's
one resolver was held and pinned elsewhere.
 2026-10-05 21:14:01 +02:00
jochen 853be00ebe The runtime's file is the runtime module's: the resolver test expects docker to write live-restore (issue 190, ADR 0196) 
The catalogue moves daemon.json's live-restore and the reload from resolv-conf to the docker
module, so no module writes another software's configuration. The test composes docker beside
the resolver modules and refuses resolv-conf writing the runtime's file.
 2026-10-05 21:14:01 +02:00