jschoubben
b9ec1919b8
mesh/repo-check head b9ec1919b865 merged into trunk a3c965b9a0d5 beside mesh-catalog#423@12ff1cfb — pass: its merge-check.sh passed
mesh/merge-gate head b9ec1919b865 merged into trunk a3c965b9a0d5 — pass: group feat/the-checker composed: every machine composes with the change as it did …
mesh/delivery delivered
mesh/delivery-group group feat/the-checker delivered: every member is delivered
36 lines
2.3 KiB
Plaintext
36 lines
2.3 KiB
Plaintext
What a test reads of another repository when no merge check has cloned it beside this one (internal/beside,
|
|
novox/hq issue 432). Copied from the repositories at the commits below, never written by hand. Each
|
|
module.json is kept as module.json.captured: a module.json in this repository is a module of it to the
|
|
forge and the planner, and a merge would build and register it.
|
|
|
|
The copy carries the catalogue's private details: domains, first names in module names, a node name and
|
|
private addresses. That is acceptable while mesh-controller is private; if it ever goes public, this copy is
|
|
a second place to clean besides the catalogue itself.
|
|
|
|
mesh-catalog e0bc919d4945bb5f13f971f74643a0b714cf45da modules/*/module.json, modules/nats/Dockerfile
|
|
mesh-host 9d9e3a46c4f5943cfffb413d962ce48b75e2fd39 examples/foundation-first-node.lock
|
|
mesh-sdk 580da61a9107f74fbef33388ece982e1b9a2e483 conformance/events/module-event.json
|
|
|
|
To move them, from this repository's root, with the two repositories checked out beside it:
|
|
|
|
rm -rf testdata/beside/mesh-catalog testdata/beside/mesh-host
|
|
mkdir -p testdata/beside/mesh-catalog testdata/beside/mesh-host
|
|
git -C ../mesh-catalog archive <commit> modules | tar -x -C testdata/beside/mesh-catalog --wildcards \
|
|
'modules/*/module.json' 'modules/nats/Dockerfile'
|
|
find testdata/beside -name module.json -exec mv {} {}.captured \;
|
|
git -C ../mesh-host archive <commit> examples/foundation-first-node.lock | tar -x -C testdata/beside/mesh-host
|
|
|
|
and write the commits here. The SDK is captured at the commit go.mod pins for git.novox.be/novox/mesh-sdk/go
|
|
(the last part of its pseudo-version; novox/hq issue 449), which internal/link's conformance test holds it to:
|
|
|
|
rm -rf testdata/beside/mesh-sdk && mkdir -p testdata/beside/mesh-sdk
|
|
git -C ../mesh-sdk archive <commit> conformance/events | tar -x -C testdata/beside/mesh-sdk
|
|
|
|
And from mesh-host at the same commit as its line above, the node-engine's placement guard, which
|
|
mesh-sdk's go/catalogue engine_guard_test.go holds the controller's resolved-path rules to (novox/hq issue 496),
|
|
kept as .captured so no Go tool reads it as this repository's code:
|
|
|
|
mkdir -p testdata/beside/mesh-host/internal/apply
|
|
git -C ../mesh-host show <commit>:internal/apply/placement_guard.go \
|
|
> testdata/beside/mesh-host/internal/apply/placement_guard.go.captured
|