Consul KV Idempotency Under Service Mesh Retry Rerouting
When Consul service mesh health checks trigger request retries, the underlying HTTP layer may re-invoke downstream service calls without preserving the Consul session identifier and prior write index that guarantee idempotent KV operations. The documented Compare-and-Swap pattern requires the caller to supply both the session ID and the index from the previo
consul