A keep wait on a filesystem that cannot carry ACLs is not excused, and nothing is asked; one whose filesystem must first enable them says in the ask that the take sets it. The tool runner's account is sent with no uid, for the engine to resolve by name.
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 b9de001833b1b61b297182b8e3bcdae1cbdeace9 modules/*/module.json, modules/nats/Dockerfile
|
|
mesh-host 8b2d65072cd825ba3ebe9a8b1e94ebc7ce046b59 examples/foundation-first-node-nats.lock
|
|
mesh-sdk 33917f91ac3cc213b879b32f3c70e2aa70395f98 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-nats.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
|
|
internal/catalogue's 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
|