novox/mesh-controller

Move route-proxy's program into its module and run it on the pinned alpine image (issues 1633, 1634, 1635, ADR 0480 §1-§4, §11) #433

Merged

mesh-tools merged 3 commits from feat/r4d into main

2026-10-22 12:19:08 +00:00

Author	SHA1	Message	Date
jschoubben	01f615aa0a	Read the bus release from the nats module's upstream artifact, so the tests' bus is still held to the mesh's once the Dockerfile is gone (issue 1640) mesh/merge-gate head 01f615aa0ad6 merged into trunk aa9da942606d — pass: group feat/r4d composed: every machine composes with the change as it did without … Details mesh/delivery delivered Details mesh/repo-check head 01f615aa0ad6 merged into trunk aa9da942606d — pass: its merge-check.sh passed Details mesh/delivery-group group feat/r4d delivered: every member is delivered Details mesh/check failed: unit: ..test: node:internal/modules/esm/resolve:241 \| 01f615aa0ad6 on aa9da942606d \| unit 3345 run, 0 kept, 7 skipped \| integration… mesh-catalog #434 runs the nats server as the upstream image named in module.json (ADR 0497) and deletes modules/nats/Dockerfile, so the check failed opening it. The manifest's upstream nats artifact is read first; the Dockerfile only for a catalogue from before the move (the captured copy).	2026-10-22 13:38:00 +02:00
jschoubben	707bfba4ea	Check an image's Dockerfile place instead of refusing the image kind (ADR 0487 clause 13) mesh/delivery-group group feat/r4d rejected: a member's own check failed Details mesh/merge-gate waits for its group's composed check Details mesh/repo-check head 707bfba4ea36 merged into trunk 4463991e0609 beside mesh-catalog#434@68183ee4 — fail: its merge-check.sh failed: --- FAIL: TestTheBusTh… Details mesh/delivery superseded: a newer head of the same pull request Details mesh/check failed: unit: i3/cmd/i3-tools.TestTheMainFileAndEveryModulesContributionLoadTogether: manifest_test.go:247: expected the launcher, clipboar…	2026-10-22 11:45:06 +02:00
jschoubben	499ff5c218	Move the route proxy into its module and run it from the trust image, on mesh-sdk's public membership (issues 1633, 1634, 1635) mesh/repo-check out of date: judged beside mesh-catalog#434 at c948f3a61c74, it is now at 7451e7edf4e5; judged again on a recheck or when it is merged Details mesh/merge-gate group feat/r4d: composed again for the group's new heads Details mesh/delivery superseded: a newer head of the same pull request Details mesh/delivery-group group feat/r4d rejected: a member's own check failed Details mesh/check failed: unit: i3/cmd/i3-tools.TestTheMainFileAndEveryModulesContributionLoadTogether: manifest_test.go:247: expected the launcher, clipboar… A bundle is built only from its module's directory (ADR 0480 clause 4), so the proxy leaves examples/ and the controller's internal/broker; the broker keeps no second copy of what the proxy shares with mesh-sdk. The image and its Dockerfile go, and a test holds that only build-agent declares one (clause 11).	2026-10-22 09:53:56 +02:00