Overview
Tracking issue for the POCS v1.0.0 milestone. The goal is a POCS that uses a file-based config store (no HTTP server), the new telemetry server (no PanDB), and lays the groundwork for running hardware components as independent processes.
Related PRs / Issues
To-Do
Config Store (PR #1448 + #1453)
Telemetry Server (PR #1445)
Terminal TUI — #1446
Hardware Decoupling (groundwork)
Release
Overview
Tracking issue for the POCS v1.0.0 milestone. The goal is a POCS that uses a file-based config store (no HTTP server), the new telemetry server (no PanDB), and lays the groundwork for running hardware components as independent processes.
Related PRs / Issues
config/store.py(merged ✓)To-Do
Config Store (PR #1448 + #1453)
config_host/config_portno-op params fromPanBaseand the CLIconfig_fileparam toPanBase.__init__so hardware processes can callinit_config(config_file)independentlyPOCSConfigPydantic validation intoinit_configso bad config fails loudly at startupdb:sections from YAML config filesTelemetry Server (PR #1445)
self.db.*call sites work withTelemetryClientdrop-in interfacepanoptes.utils.database(PanDB) dependency frompyproject.tomldb:sections from YAML config filespocs telemetry run/pocs telemetry currentCLI commandsmake_firestore_hook)scheduling.py/parking.py/__init__Terminal TUI — #1446
bridge.pycommand channel +pocs tuiCLI entry point_scan()reading from TelemetryClient → POCSModel)Hardware Decoupling (groundwork)
config_fileparam and callsinit_configindependentlyRelease
CHANGELOG.mdwith all v1.0.0 entries1.0.0inpyproject.tomldocs/tui_plan.md) before mergingv1.0.0→mainv1.0.0