jochen
dd89b6e800
mesh/delivery-group group fix/383-an-ask-reads-at-a-glance checking: 1 of 2 member(s) ready
mesh/merge-gate out of date: judged against trunk 9f3aa91e812b, the trunk is now 332fbaa9b175; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against trunk 9f3aa91e812b, the trunk is now 332fbaa9b175; judged again on a recheck or when it is merged
mesh/delivery superseded: a newer head of the same pull request
{a:1, b:2, c:3, password:hunter2} was proposed with "+ password: hunter2" in its Details: the router
withheld the line unnamed and Approve set a value the operator never saw (ADR 0347 §1, §3, §4). Each line is
now judged as the router judges it, masked under the content rule and whole under the secret rule; a line
refused is said "+ password (value withheld)", and any line the router would still refuse is refused at
propose in the controller's words, never echoing a secret-shaped key. SDK at mesh-sdk 5933eb7 (no two asks
digest the same).
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 7a41e120635b3f7b6cb94cca8b3fc4093e4e6110 examples/foundation-first-node.lock
|
|
mesh-sdk 5933eb757d443293631be2bed27a96288c2348d8 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
|
|
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
|