Alan-Jowett / sonde / 25953392533

81%

push

github

feat(azure-handler): implement SensorData table storage (AZH-0500, AZH-0501) (#931)

* feat(azure-handler): implement SensorData table storage (AZH-0500, AZH-0501)

Extract enriched \eadings\ (CBOR key 16) from \GW-0813\ APP_DATA
connector messages and write a \SensorData\ row for every app-data
invocation.

Changes:
- Add \eadings: Option<BTreeMap<String, i64>>\ to \AppDataMessage\
- Add \decode_optional_readings()\ to extract CBOR key 16 map
- Add \SensorDataRow\ / \SensorDataEntity\ types
- Add \eadings_to_json()\ with \MAX_SAFE_INTEGER\ threshold:
  values within ±2^53-1 are JSON numbers, values exceeding that
  threshold are JSON strings to preserve precision for SPA consumers
- Add \ppend_sensor_data()\ to \HandlerStore\ trait
- Add \sensor_data_table\ to \RuntimeConfig\ and \AzureTablesStore\
- Write SensorData row before ProgramRoute lookup in \handle_app_data\,
  per design §6.1 (SensorData writes are independent of routing)

Tests added:
- T-AZH-0500: basic row creation
- T-AZH-0500a: duplicate-timestamp uniqueness
- T-AZH-0501: readings stored as JSON
- T-AZH-0501a: missing readings → empty string
- T-AZH-0501b: large int64 threshold (positive and negative)
- SensorData written even when ProgramRoute missing
- \eadings_to_json\ edge cases (None, empty, boundary, i64::MIN)
- \SensorDataEntity\ conversion round-trip

Known limitations:
- T-AZH-0500b (retry idempotency) requires passing upstream queue
  message ID through \handle_payload\ — deferred to a follow-up
- AZH-0500 AC-4 (Bicep provisioning) is infrastructure-only

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Alan Jowett <alan.jowett@microsoft.com>

* infra: provision SensorData table and RBAC (AZH-0500 AC-4)

Add the \SensorData\ Azure Table to the Bicep provisioning stack so
the Azure handler can write enriched APP_DATA rows at runtime.

Changes across the deployment chain:
- storage.bicep: new \sensorDataTableName\ param, table resource, ... (continued)

349 of 361 new or added lines in 1 file covered. (96.68%)

35243 of 42486 relevant lines covered (82.95%)

255.87 hits per line