+1 (non-binding)
+1 (non-binding) +1 (non binding)
Regards JB
Hi Everyone,
As we discussed before in the idempotency spec, having an idempotency key in a mutating endpoint is really beneficial incase of clients HTTP retries per [1] (Thank you Huaxin for driving it)
I want to propose adding idempotency keys to plan endpoint too, since some of them are mutating endpoints having idempotency key for them would be helpful for the server to make the call incase the client retries the same request, as the course of that i have created a spec PR [2] for the same.
Please vote in the next 72 hours.
[ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason
|