v0.15.4: Hub disabled notification, PushOnce, ReportingDisabled field
This commit is contained in:
@@ -1,5 +1,15 @@
|
||||
## Changelog
|
||||
|
||||
### What was just completed (2026-02-19 session 54)
|
||||
- **v0.15.4 (controller) + hub v0.1.6 — Hub reporting improvements:**
|
||||
|
||||
**Controller:** When `hub.enabled: false` but URL+API key are configured, the controller now creates the `Pusher` and sends a one-time "disabled" notification on startup (`health.status = "disabled"`, `reporting_disabled: true`). This replaces the old behavior where a disabled controller was indistinguishable from a crashed node. Added `PushOnce()` method to `Pusher` (bypasses the `enabled` flag). Added `ReportingDisabled` field to the `Report` struct.
|
||||
|
||||
**Hub:** Added "disabled" status handling — when the latest report has `health_status = "disabled"`, the overall status is "disabled" (checked BEFORE the stale-time logic, so it stays "PAUSED" even after 30min+). Dashboard shows gray "PAUSED" badge. Customer detail shows "Reporting has been disabled on this node" with a hint to re-enable. Storage labels now shown (`label` field with fallback to `mount`). Report history timestamps now show date + time ("Feb 19 09:46" instead of "09:46:54"). New `.status-badge-disabled` CSS (neutral gray `#475569`).
|
||||
|
||||
**Files modified (controller):** `internal/report/types.go`, `internal/report/pusher.go`, `cmd/controller/main.go`
|
||||
**Files modified (hub):** `hub/internal/web/server.go`, `hub/internal/web/templates/dashboard.html`, `hub/internal/web/templates/customer.html`, `hub/internal/web/templates/style.css`
|
||||
|
||||
### What was just completed (2026-02-19 session 53)
|
||||
- **v0.15.3 — Show all storage paths on dashboard + fix hub report:**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user