19 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	16331cdfdc	Fill a module again when the node-engine's socket returns after any failed fill, not only one for want of the socket (issue 1873) ... On ace postgres's fill of superuser.secret failed at 22:12 with the engine's own "is a directory", what a container runtime had left at the path. The engine delivered at 22:42 clears such a directory, but the client tried again only modules whose fill had failed for want of the socket (issue 1165), so postgres was never filled again and its old failure was said every 30 s. A newer engine may write what the older could not: any failed fill is now tried again when a node-engine makes its socket again.	2026-10-22 22:56:16 +02:00
jschoubben	ab3722d3b3	Test that a fill the node-engine failed is tried again when its socket returns (issue 1873)	2026-10-22 22:53:39 +02:00
jschoubben	7bf0de0ff5	Move the socket-return fill tests (issue 1165) to the integration level: they make a real socket and watch its directory	2026-10-21 21:57:53 +02:00
jschoubben	d9876e5296	Merge remote-tracking branch 'origin/fix/1165-fill-retry' into feat/the-checker ... # Conflicts: # modules/mesh-provisioner-client/cmd/mesh-provisioner-client/client_test.go	2026-10-21 21:50:26 +02:00
jschoubben	0cf7b2344f	Write a moved contributor's declared defaults into the provisioner client tests' stand-in mesh-config (issue 1780)	2026-10-21 21:48:59 +02:00
jschoubben	aa5d263c08	Test the returning socket by a real restart of the stand-in node-engine	2026-10-21 21:45:34 +02:00
jschoubben	769a8d6f6a	Fill again what failed for want of the node-engine's write socket, when inotify says the socket is back (issue 1165)	2026-10-21 21:45:13 +02:00
mesh-tools	37035dfc90	Fill a module's files one by one, so a known secret's file is not held back by a template that waits (issue 1553)	2026-10-21 00:00:09 +00:00
jochen	e7ff7c3045	Write a provisioner client's files only on a change over the bus, never on a timer (issue 1129, ADR 0349 clause 4)	2026-10-18 18:08:50 +02:00
jschoubben	68e3326d4c	Providers and the provisioner client take the SDK that reads an ended assignment as a removed key (issue 1098)	2026-10-18 02:40:18 +02:00
jschoubben	9edd16eaeb	mesh-provisioner-client takes a module off the node when its assignment is ended (issue 1098)	2026-10-18 02:37:28 +02:00
lead-57	4215b40547	Read the whole plan the controller writes: at, from, as, names and credential-tool (issue 954) ... The client decodes a plan strictly, and since the controller carries these fields (issues 923 and 928) it refused the plans of gitea, keycloak and claude-code.	2026-10-16 21:32:13 +02:00
fix-cat-pas@novox	dcedd8d2b2	Give the route plan entries their credential-form, and read the entry's vault-name in the route providers' tests (issues 923, 945)	2026-10-16 19:44:19 +02:00
fix-vault-pas@novox	2f09dd8501	Merge branch 'feat/providers-after-switch-on' into feat/providers-after-switch-on-v	2026-10-16 19:34:15 +02:00
fix-vault-pas@novox	044a548cee	Pin that the client asks a refused or not-yet secret again (issue 928)	2026-10-16 19:31:40 +02:00
fix-cat-pas@novox	0b056edaaa	Prove the client fills gitea's origins and keycloak's hostname from route-proxy's entry for a controller-shaped plan entry (issue 923)	2026-10-16 19:29:30 +02:00
fix-cat-pas@novox	cc9e7a72ee	Name the vault's credential vault-name in the client's bound-entry fixtures (issue 945)	2026-10-16 19:29:30 +02:00
mesh-tools	a31ad48b02	Restore the blank last line the patch route dropped from ten files, so the branch holds the reviewed tree (issue 875)	2026-10-16 09:43:59 +00:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00