Update existing service instance: not able to delete while update in progress about servicebroker HOT 2 CLOSED

It's up to the broker if and when concurrent operations are allowed. The spec says this:

Service Brokers MAY choose the degree to which they support concurrent requests, ranging from not supporting them at all to only supporting them in selective situations. If a Service Broker receives a request that it is not able to process due a concurrency issue then the Service Broker MUST reject the request with a HTTP 422 Unprocessable Entity and a response body containing error code "ConcurrencyError" (see Service Broker Errors).

The first scenario is also explicitly covered by the spec:

If a Service Broker accepts the request to delete a Service Instance during the process of it being provisioned, then it MUST have the net effect of halting the current creation process and beginning the deletion of any resources associated with the Service Instance.

In the second scenario, the broker returns the wrong status code, though.

Does this answer your question? If so, please close this issue.

from servicebroker.

Closing this as the question was answer and there wasn't activity ever since.

from servicebroker.