gateway: AcknowledgeAlarm + QueryActiveAlarms RPC handlers (PR A.3) #111
Reference in New Issue
Block a user
Delete Branch "track-a3-gateway-alarm-handlers"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Twelfth PR of the alarms-over-gateway epic. Lands the public RPC handler surface that PR A.1's proto introduced. Actual worker-side ack call + active-alarm walk depend on PR A.2 (worker MxAccess subscription); this PR ensures clients can call the RPCs and receive a meaningful response without UNIMPLEMENTED at the gRPC layer.
AcknowledgeAlarm— validates session_id + alarm_full_reference, resolves the session (NotFound on miss), returns a successful reply with a structured DiagnosticMessage indicating worker dispatch is pending A.2.QueryActiveAlarms— validates session_id, returns an empty stream. PR A.4 layers the actual ConditionRefresh implementation.OpenSessionReply.Capabilitiesadvertises both new RPCs (unary-acknowledge-alarm,server-stream-active-alarms).OnAlarmTransition events already flow through
StreamEventsautomatically —EventStreamServiceandMxAccessGrpcMapperforward whatever family the worker emits without filtering, so no changes were needed there.Test plan
Per-handler unit tests ship with PR A.4's expanded surface.