mirror of https://gitee.com/pnoker/iot-dc3.git synced 2026-11-01 02:31:46 +08:00

Files

T

History

pnokerandClaude Code 98c0f8a6c3 fix(ci): sync the mockito integrity pin and document the insight rpc

The mockito jar sha1 pin still targeted the pre-upgrade artifact while
the build resolves 5.24.0, so every CI run failed the agent-integrity
check even after refetching. Re-pin to the 5.24.0 jar sha1 verified
against Maven Central metadata.

Document the InsightApi.Invoke RPC in the dc3-api-data README so the
proto-to-documentation guard passes.

Co-Authored-By: Claude Code <noreply@anthropic.com>

2026-10-09 00:25:11 +08:00

src/main/protobuf/api/common/data

feat(data): add the agent-facing insight channel with history facades

2026-10-08 00:08:24 +08:00

pom.xml

docs(release): update generated changelog and bump to 2026.10.9

2026-10-09 00:16:02 +08:00

README.md

fix(ci): sync the mockito integrity pin and document the insight rpc

2026-10-09 00:25:11 +08:00

README.md

DC3 API Data

dc3-api-data defines gRPC contracts for values, commands, events, status, and system-health queries. Generated Java types use io.github.pnoker.api.center.data; proto sources live under src/main/protobuf/api/common/data/.

Services

Service	RPCs	Purpose
`PointValueApi`	`GetLastValue`, `ListHistoryValues`, `ListSeriesVolumes`	query point values and value-volume series
`PointValueApi`	`ReadCommand`, `WriteCommand`	submit point read/write commands
`CommandHistoryApi`	`CallCommand`, `GetByRecordId`, `List`	dispatch and query command history
`EventHistoryApi`	`ReportEvent`, `GetByRecordId`, `List`	report and query event history
`StatusHealthApi`	`DeviceStatusesByIds`, `DeviceStatusesByProfileId`	query device status snapshots
`StatusHealthApi`	`DriverStatusesByIds`, `DriverDeviceStatusSummary`	query driver status snapshots and device summaries
`StatusHealthApi`	`SystemHealth`	query the platform health snapshot
`InsightApi`	`Invoke`	agent-facing insight channel: JSON-payload reads

Single-result RPCs use GetXxx; collection/page results use ListXxx or an explicitly named status aggregation. Do not reintroduce legacy SelectXxx names.

Consumers and implementation

dc3-common-data implements the data-side servers.
dc3-common-facade-grpc wraps generated stubs in transport-independent facades.
Manager and other business modules should call the facade API rather than construct channels directly.

All write/report requests must carry tenant context through the transport and into the business layer.

Build and Verification

mvn -s .mvn/settings.xml -q -pl dc3-api/dc3-api-data -am compile

This contract module has no module-specific tests. Compile it after proto changes, then run the matching server and facade tests in dc3-common-data and dc3-common-facade-grpc.