jschoubben
67d8d0dcbd
The review found broker own-secret paths drifting: mostly /var/lib/<module>/ broker, but grafana/redis/icecast/nextcloud carried a '-module' suffix to dodge a collision with the service's own /var/lib/<name> data, and photos sat under /etc. Normalized to one collision-free namespace a service never owns: /var/lib/mesh/<module>/broker, with a mesh-state directory resource for the parent, across 24 modules. audit-logger is grandfathered (lab-proven, referenced by the assigned test, and it has no service to collide with). All 33 manifests parse; no client hardcoded a path, so nothing in code moved. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
50 lines
1.0 KiB
JSON
50 lines
1.0 KiB
JSON
{
|
|
"module": "home-assistant",
|
|
"version": "1",
|
|
"capabilities": [
|
|
"container-runtime"
|
|
],
|
|
"emits": [
|
|
"module.home-assistant.state.changed"
|
|
],
|
|
"own-secrets": {
|
|
"broker": "/var/lib/mesh/home-assistant/broker"
|
|
},
|
|
"listens": [
|
|
{
|
|
"port": 8123,
|
|
"protocol": "tcp",
|
|
"from": "mesh",
|
|
"why": "the dashboard and the API"
|
|
}
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "mesh-state",
|
|
"type": "directory",
|
|
"path": "/var/lib/mesh/home-assistant",
|
|
"mode": "0700"
|
|
},
|
|
{
|
|
"id": "config",
|
|
"type": "directory",
|
|
"path": "/services/home-assistant/config",
|
|
"mode": "0700",
|
|
"owner": "1000:1000"
|
|
},
|
|
{
|
|
"id": "server",
|
|
"type": "container",
|
|
"name": "home-assistant",
|
|
"image": "ghcr.io/home-assistant/home-assistant@sha256:14931c6b13756317849f46da1d01b45937a1150db66c081cfe529d48215943fe",
|
|
"network": "host",
|
|
"env": {
|
|
"TZ": "Etc/UTC"
|
|
},
|
|
"volumes": [
|
|
"/services/home-assistant/config:/config"
|
|
]
|
|
}
|
|
]
|
|
}
|