prisma-risk / tsoracle / 26390362787

95%

push

github

feat(driver-openraft)!: membership-driven peer addressing (#408)

* feat(driver-openraft)!: carry a service endpoint on OpenraftPeer

Add a service_endpoint field beside addr and a ServiceEndpoint trait so the
membership Node carries the tsoracle client URL alongside the raft peer URL.
Breaking: widens the OpenraftPeer postcard layout.

* feat(openraft-toolkit)!: bump SCHEMA_VERSION to 3 for widened OpenraftPeer

The membership node layout changed; a v2 store loud-rejects against v3.
Breaking on-disk: requires a fresh cluster for every toolkit consumer.

* feat(example-piggyback): implement ServiceEndpoint for HostPeer

The KV demo carries no client redirect, so it returns None; satisfies the
driver's ServiceEndpoint bound.

* feat(driver-openraft)!: resolve follower redirects from membership

Drop the static peers map and the with_peers/from_arc_with_peers constructors;
read the leader's service_endpoint from the live membership node via the new
ServiceEndpoint bound. Breaking: removes the with_peers constructors.

* feat(example-standalone): drive raft transport from membership addr

Dial node.addr from membership instead of a static map, key the pool by
(NodeId, addr), and evict the cached client on transport failure so a redial
re-resolves the stable DNS name to the rescheduled pod's new IP.

* docs(example-standalone): document stable-DNS addressing and fresh-cluster requirement

Also update the three SCHEMA_VERSION pin tests in tsoracle-driver-openraft
from v2 to v3, matching the version bump introduced earlier in this branch
when OpenraftPeer gained the service_endpoint field.

* docs(driver-openraft): document service_endpoint as scheme-less host:port

The client normalizes a bare host:port to its own scheme (https under TLS,
http otherwise) and a TLS client refuses an explicit http:// hint, so the
portable membership value is scheme-less.

* test(driver-openraft): pin the populated OpenraftPeer postcard layout

The v3 frame pins serialize emp... (continued)

91 of 91 new or added lines in 4 files covered. (100.0%)

9269 of 9690 relevant lines covered (95.66%)

499042.66 hits per line