Nothing has claimed node-dns-resolver since the mesh moved to one resolver (hq ADR 0194); seeding never removes a row, so a migration deletes it. resolv.conf stays the mesh's only while the network manager is told to keep off it, which the node-uplink holder does (ADR 0117). A seat's Needs makes that a dependency checked at assignment by the ADR 0207 mechanism (hq ADR 0220). The two-claimants test keeps its intent with a synthetic module now that resolved-split-dns leaves the catalogue.
18 lines
1.1 KiB
SQL
18 lines
1.1 KiB
SQL
-- The per-node resolver's seat is gone (novox/hq ADR 0220, retiring what ADR 0194 decided).
|
|
--
|
|
-- ADR 0194 retired `node-dns-resolver` when the mesh moved to one resolver, and kept its row while a
|
|
-- machine still held it: removing a seat that is claimed makes the claiming machine unresolvable. On
|
|
-- the mesh this was written for, nothing has held it since every node's resolver moved to the mesh's
|
|
-- one, and no module in the catalogue claims it, so the row goes.
|
|
--
|
|
-- **The compiled defaults no longer carry it, and that alone would not remove it.** Seeding adds a
|
|
-- seat a release ships and never takes one away (ADR 0122: the table is the live set, and an
|
|
-- operator's row is left as it is), so a seat the mesh stops defining stays in the table until
|
|
-- something deletes it — this.
|
|
--
|
|
-- A holding on record goes with it by cascade; there is none. No alias is kept: nothing was renamed,
|
|
-- and a manifest still claiming the old name should be refused at registration, naming it, rather
|
|
-- than resolve to anything.
|
|
delete from seat_alias where seat = 'node-dns-resolver' or alias = 'node-dns-resolver';
|
|
delete from seat where name = 'node-dns-resolver';
|