Operator ruling: NEVER force a reconnect on a routine reload/rpc-update run. Only upstream REMOVALS or new disabled-method ADDITIONS require a gateway reconnect to be seen by dRPC gateways. Implement snapshot-based comparison: - Before SIGHUP, read current advertised set (upstream IDs + disabled methods) - Compare against previous snapshot (if exists) - Drop established gRPC connections ONLY IF: * an upstream ID disappeared, OR * a new disabled-method entry appeared - Pure additions or no change: reload only, no drop - First run with no prior snapshot: do NOT drop, just write snapshot - Always rewrite snapshot after successful reload - All operations best-effort (failures never fail the script) Live-measured: upstream/method additions propagate over existing connection in ~16s (no reconnect needed). Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
11 KiB
Executable File
11 KiB
Executable File