The artifact store requires nothing, because at genesis there is nothing
A route-label migration gave the registry a public name, and with it a requirement. But the registry is the first module a new mesh installs: at that moment nothing provides a route, so the push is refused and a mesh cannot get its own image store — the cycle 04-ISSUES/029 closed, re-entered through a different door. The same rule that record states applies: a module providing the artifact store cannot depend on what the store is needed to deliver. A public name for it is an ordinary want and belongs to a module beside it, installed once there is a mesh to install things. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
This commit is contained in:
@@ -54,17 +54,5 @@
|
|||||||
"mesh-registry-data:/var/lib/registry"
|
"mesh-registry-data:/var/lib/registry"
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
],
|
]
|
||||||
"requires": [
|
|
||||||
"route"
|
|
||||||
],
|
|
||||||
"contributes": {
|
|
||||||
"route": {
|
|
||||||
"label": "registry-api",
|
|
||||||
"port": 5000
|
|
||||||
}
|
|
||||||
},
|
|
||||||
"binds": {
|
|
||||||
"route": "/var/lib/mesh/registry/route.json"
|
|
||||||
}
|
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user