clients: regenerate Python + Go protos for alarm RPCs (PR E.1) #105
Assignees
dohertj2 (dohertj2)
Clear assignees
dohertj2 (dohertj2)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: dohertj2/mxaccessgw#105
Reference in New Issue
Block a user
Delete Branch "track-e1-proto-regen"
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
Mechanical regen of client-side proto bindings following PR A.1 (#104). Ran the per-language scripts:
clients/python/generate-proto.ps1→mxaccess_gateway_pb2.py+mxaccess_gateway_pb2_grpc.pyclients/go/generate-proto.ps1→mxaccess_gateway.pb.go+mxaccess_gateway_grpc.pb.go+ a whitespace diff ingalaxy_repository.pb.goThe .NET binding regenerates on csproj rebuild via Grpc.Tools — its
Generated/MxaccessGateway*.cswas committed as part of A.1. Java + Rust regen at build time via the gradle plugin / build.rs respectively; no committed output to refresh.Verified the new types are wired into the regenerated bindings:
Test plan
python generate-proto.ps1runs cleango generate-proto.ps1runs clean_pb2module exposes the new typesOnAlarmTransitionEvent,ActiveAlarmSnapshot,AcknowledgeAlarmRequest,AcknowledgeAlarmReply,QueryActiveAlarmsRequestFollow-up
E.2 - E.6 layer hand-written SDK methods (alarm subscribe/ack/query verbs) on top of the regenerated types — independent per-language PRs.
Pure mechanical regen following PR A.1 (alarm-transition event family + AcknowledgeAlarm / QueryActiveAlarms public RPCs). Ran: - clients/python/generate-proto.ps1 → mxaccess_gateway_pb2.py + mxaccess_gateway_pb2_grpc.py. - clients/go/generate-proto.ps1 → mxaccess_gateway.pb.go + mxaccess_gateway_grpc.pb.go + galaxy_repository.pb.go (whitespace diff from upstream protoc minor version). The .NET binding regenerates on csproj rebuild via Grpc.Tools — its artifact (Generated/MxaccessGateway*.cs) was already updated as part of A.1's commit. Java + Rust regen happens at build time via the gradle plugin / build.rs respectively, with no committed output to update. Smoke-imported the regenerated Python descriptors: OnAlarmTransitionEvent.DESCRIPTOR.fields → alarm_full_reference, alarm_type_name, category, current_value, description, ... AcknowledgeAlarmRequest.DESCRIPTOR.fields → alarm_full_reference, client_correlation_id, comment, operator_user, session_id ActiveAlarmSnapshot.DESCRIPTOR.fields → alarm_full_reference, alarm_type_name, category, current_state, current_value, ... PRs E.2 - E.6 layer hand-written SDK methods on top of the regenerated types — those land per-language as separate PRs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>