The control plane prepares its own state, like any module
Now that every parser on the mesh knows the word, the control plane's manifest says it. Its schema stops being a special case: the mesh derives the step from its own resource and gates its server on it, which is the failure of novox/hq 04-ISSUES/133 closed by the mechanism rather than by a hand-written step in one manifest.
This commit is contained in:
@@ -27,6 +27,7 @@
|
|||||||
"bus": "/var/lib/mesh/mesh-controller/bus"
|
"bus": "/var/lib/mesh/mesh-controller/bus"
|
||||||
},
|
},
|
||||||
"secrets-owner": "65534:65534",
|
"secrets-owner": "65534:65534",
|
||||||
|
"prepares": true,
|
||||||
"resources": [
|
"resources": [
|
||||||
{
|
{
|
||||||
"id": "mesh-state",
|
"id": "mesh-state",
|
||||||
|
|||||||
Reference in New Issue
Block a user