Download this file
| 1 | # Fast config convergence for unit-backed apps (issue #44). The agent's |
| 2 | # configGenLoop touches this file when a config write moves the generation |
| 3 | # object of an app with carlos-app@ routes on this box: the agent renders |
| 4 | # exec-backed instances itself, but it cannot write /etc/carlos/apps or |
| 5 | # restart units, so it asks a root pass to do both. It starts |
| 6 | # carlos-config-sync.service — the CONFIG half alone, deliberately NOT |
| 7 | # carlos-adopt.service: a per-config-write trigger must never run release |
| 8 | # adoption or the canary-TTL nag, which stay on carlos-adopt.timer's hourly |
| 9 | # cadence. /data is hardcoded like every path in these unit files — a box |
| 10 | # with a nonstandard data dir simply never fast-triggers and keeps that |
| 11 | # hourly floor. |
| 12 | [Unit] |
| 13 | Description=CARLOS config sync on agent request (config fast convergence) |
| 14 | |
| 15 | [Path] |
| 16 | PathChanged=/data/config-sync-requested |
| 17 | Unit=carlos-config-sync.service |
| 18 | |
| 19 | [Install] |
| 20 | WantedBy=multi-user.target |
| 21 | |
amadan