5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	ddae6729c1	Give route-proxy its state on the bus and three tools, so a site's route, certificate and last answer are read from the mesh instead of with curl (issue 774) ... The web front kept nothing on the bus: whether grafana or drive was routed, where to, with which certificate, and what it last answered could only be learned with curl or the container's log. The proxy now keeps `routes` and `unrouted` (announced readable, keyed <node>.<name>), written on change by one writer: route set changes, certificates stored by autocert's cache or failing at a handshake, upstream answers that differ from the last written (or are a minute old), and names refused in a request or a handshake. The provider helper's bundle serves route_proxy_routes, route_proxy_route and route_proxy_unrouted from those states. Quick: log the routes at start and grep the journal. Thorough: the state on the bus and the tools that read it, mesh-wide, in one call. Chose thorough: the operator's question is mesh-wide and recurs, and the log says nothing about certificates or answers. Tests: two table tests added (the ledger, the tools), both failing without the change; four authority tests and four skipped-route tests merged into two, so the module has four fewer.	2026-10-30 22:58:04 +01:00
jschoubben	899389c710	Reword route-provider's stdout line, so route-proxy's tree differs from the 01:52 build whose files are gone (issue 1933)	2026-10-24 02:50:12 +02:00
jschoubben	a203f605d4	Give route-proxy a build the fixed controller takes in, dropping the incident note #450 added (issue 1933)	2026-10-24 02:49:56 +02:00
jschoubben	f13d42abb4	Give route-proxy a new build: the controller's sweep removed its last build's files from the store, so novox and ace cannot apply (issue 1933)	2026-10-24 02:37:06 +02:00
jschoubben	1586bd1134	Bring build-agent and route-proxy in whole (issue 1019)	2026-10-17 18:15:33 +02:00