Closed kibbles-n-bytes closed 5 years ago
I would support expanding the error to cover both.
Agreed. Can you submit a PR @kibbles-n-bytes ?
The binding section in the spec now says:
Additionally, if the Service Broker rejects the request due to a concurrent request to create a Service Binding for the same Service Instance, then this error MUST be returned (see Blocking Operations).
Closing this!
The spec says that for the "concurrent requests that mutate the same resource", it is expected that the error response from the broker contains the "ConcurrencyError" error code. What about in the case that the broker is rejecting a concurrent bind request? Is it expected/acceptable for the broker to use this error code?