v0.334.0: a live box refreshes its config with its own hub key (GET /box-config; R-1159, operator D19)
gates / gates (push) Successful in 49s
gates / gates (push) Successful in 49s
This commit is contained in:
@@ -3155,6 +3155,10 @@ bumped on every config save; felhom-hub v0.26.0). This is how an operator config
|
||||
box — **the hub never connects into the box** (it replaced the retired inbound "Push Config"). Wired in
|
||||
`OnPushResponse` beside the floor reconcile (`internal/report/config_refresh.go`, `ConfigRefresher.Reconcile`):
|
||||
|
||||
**Since v0.334.0 (R-1159) the re-pull uses the box's OWN hub key** — `GET /api/v1/box-config/{id}` (hub ≥ 0.161.0),
|
||||
`report.PullConfigPreferKey`; the retrieval passphrase only against a hub without that route or before the box has a
|
||||
key. The hub refuses the passphrase's keys once such a box has reported.
|
||||
|
||||
- **Changed** vs. the last-applied version (`settings.applied_config_version`) → `bootstrap.RefreshConfig`
|
||||
re-pulls `controller.yaml` from the hub and rewrites it, **re-merging the per-guest `local_api`** from
|
||||
`bootstrap.json` (reuses the first-boot pull machinery; overwrites `controller.yaml` since the hub is its
|
||||
|
||||
Reference in New Issue
Block a user