mesh-host

Files

T

jochen 50776b8613 review: a retired configuration that comes back is retired again on its first original, and only wg-quick's own file is ever removed (hq ADR 0119)

Put back by hand, it was found afresh and its copy became the hold's original, so a machine that
kept restoring it kept growing copies and lost which one was first. The first original now stays
the record's, content that differs is kept once beside it, and the note says a rollback means
unassigning the private network. Nothing is removed unless it is <wireguard dir>/<iface>.conf,
not a path the mesh writes, and not a link, which would leave the key-bearing target behind.

2026-09-27 00:55:50 +02:00

declared_test.go

A node that loses its mesh comes back on its own

2026-08-29 20:17:49 +02:00

declared.go

Refuse a declaration for the other mode, or older than the mesh's last, and say what an apply would change first

2026-09-23 23:15:28 +02:00

lock_test.go

Refuse every file once the mesh has spoken, plan the cutover as one, and let the kept declaration repair the mode

2026-09-23 23:35:49 +02:00

lock.go

Refuse every file once the mesh has spoken, plan the cutover as one, and let the kept declaration repair the mode