mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
ce338b1496
## Why `useWorkloadsState` defaulted `groupNodeDrawerMode` to `'inline'`, and only that mode wired group-header hover preview, click-to-pin group scope and an inline `NodeDrawer` under the group row. The only page that used the default, the standalone `/workloads` page, was retired in May. Both production mounts have passed `'disabled'` since host drawers moved to each page's own hosts table: Proxmox in84f627e22a(2026-05-18, "Move Proxmox host drawers to the host table") and vSphere ind96d5612fd(2026-05-23). The disabling was deliberate on both pages, so this removes the dead path instead of re-enabling it. The demand ledger has no entry asking for workload group hover or pin. The only way left to reach the group pin was a hand-typed `?summaryGroup=` URL. No link builder passes it, and row expansion stopped writing it in86ac84f68e. ## What changes - `WorkloadPanel`: drops the inline `NodeDrawer` mount, the group hover and pin handlers, `aria-expanded`, `data-summary-group-series-count`, `data-summary-row-active` on group rows, and the group-member state passed to `GuestRow`. Group rows stay identity-only dividers and keep `data-summary-group-id`, so clicking one still leaves an open guest drawer alone (`summaryTableFocus` ignores that selector). - `useWorkloadSelectionState`: drops the hovered and focused group scope, `summaryGroup` hydration and the related effects. It no longer passes group options to the shared bridge; Storage still uses them. - `useWorkloadsState`: drops the option, `getNodeTemperatureThresholds` (it only fed the removed drawer), and the `summaryGroupScopes` memo, which rebuilt a scope for every group on every filtered-guest change. - Removes `buildWorkloadSummaryGroupScope(Map)`, `workloadsHasVisibleWorkloadGroupScope`, the `GuestRow` group-member attribute and the workloads `summaryGroup` route param. - Proxmox and vSphere stop passing the option. Their filter bars' pinned-selection state now reads only the selected guest. - `NodeDrawer` stays live in `ProxmoxNodesTable`. The temperature guardrail now pins that live mount instead of the dead one. - Contracts: rule 8 and the Workloads, Proxmox and vSphere clauses now describe static dividers. Stale sentences about grouped node rows opening the node drawer, group-row emphasis, and Workloads selection writing back to the route are corrected. ## Verification - Before/after browser pass on pulse-dev: embedded builds on mock demo stacks, Proxmox and vSphere overviews, at 1440x900 and 390x844. - Hover, click and tap on group dividers do nothing on both builds. - Guest drawer, Escape, guest-row hover emphasis, `?resource=` links and the Proxmox nodes-table `NodeDrawer` behave the same on both builds. - Clicking a divider with a guest drawer open keeps the drawer: 10/10 on each build. - The hand-typed `?summaryGroup=` URL pinned 18 Proxmox rows on main and pins none now. - Receipt: `frontend-modern/browser-verification/db4ee39cb5db006c.json`. - Frontend typecheck passes. The targeted suites (Workloads, proxmox, vmware, platformPage, shared, routing, utils, hooks, Storage) pass on pulse-dev except one Proxmox backups windowing test that failed once at load ~40 and then passed 2/2 alone. - A full-suite run on the earlier base passed except files that also fail on unmodified main or only under load. `useReportingPanelState` fails on main there too. - Commit hook battery and governance audits pass. - Two rounds of second-opinion review. Round 1 caught a stale test pin and stale perf-contract prose; round 2 caught one inaccurate scroll-restore sentence. All are fixed here. Follow-ups raised separately: the built-in `WorkloadsSurface` filter toolbar is also unreachable, since both mounts pass `suppressFilterToolbar`. The quarantined E2E spec 48 still targets the retired `/workloads` page.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.