Tests that read ../../../mesh-catalog or ../../../mesh-host gave a verdict that depended on what sat beside the checkout: a stale or dirty sibling failed them on a desktop, and a missing one skipped them unseen. They now read the clone the build seat puts in MESH_CHECK_BESIDE, failing when it is absent there, and elsewhere a copy captured at a named commit. The skip had hidden that the builder test read a module retired by ADR 0190. The systemd reading test no longer counts the machine's own environment.d.
49 lines
1.2 KiB
Plaintext
49 lines
1.2 KiB
Plaintext
{
|
|
"module": "hostname",
|
|
"version": "1",
|
|
"claims": [
|
|
{
|
|
"name": "node-hostname",
|
|
"scope": "node",
|
|
"serves": [
|
|
"entries",
|
|
"add",
|
|
"remove"
|
|
]
|
|
}
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "own",
|
|
"type": "file",
|
|
"path": "/etc/hosts",
|
|
"mode": "0644",
|
|
"into": "block",
|
|
"at": "start",
|
|
"content": "# The machine's own names (module hostname, novox/hq ADR 0199, ADR 0223). Every line outside this\n# block is the operator's: kept across every push, changed through the node-hostname verbs add and\n# remove, and given back when this module goes. The mesh's names are not here: the mesh's resolver\n# answers them.\n127.0.0.1\tlocalhost\n::1\tlocalhost\n127.0.1.1\t${machine:name}\n"
|
|
},
|
|
{
|
|
"id": "name",
|
|
"type": "file",
|
|
"path": "/etc/hostname",
|
|
"mode": "0644",
|
|
"content": "${setting:hostname}\n"
|
|
}
|
|
],
|
|
"build": {
|
|
"artifacts": [
|
|
{
|
|
"name": "tools",
|
|
"kind": "bundle",
|
|
"language": "go",
|
|
"system": "arch",
|
|
"from": "cmd/hostname-tools",
|
|
"binary": "hostname-tools",
|
|
"loads": [
|
|
"hostname-tools"
|
|
]
|
|
}
|
|
]
|
|
}
|
|
}
|