Skip to content

fix: correct error response when attempt to delete provisioning service#1337

Merged
pivotal-marcela-campo merged 1 commit intomainfrom
delcre
Oct 16, 2025
Merged

fix: correct error response when attempt to delete provisioning service#1337
pivotal-marcela-campo merged 1 commit intomainfrom
delcre

Conversation

@blgm
Copy link
Copy Markdown
Member

@blgm blgm commented Oct 16, 2025

The broker does not support the deletion of a service while provisioning is in progress. But it does not return the correct error response. The spec says:

422 Unprocessable Entity
Additionally, this MUST be returned if the Service Instance is being processed by some other operation and therefore cannot be deleted at this time. The response body MUST contain error code "ConcurrencyError"

This commit corrects this so that the broker implements the spec correctly.

The broker does not support the deletion of a service while provisioning
is in progress. But it does not return the correct error response. The
[spec](https://github.com/cloudfoundry/servicebroker/blob/master/spec.md#deprovisioning)
says:
```
422 Unprocessable Entity
Additionally, this MUST be returned if the Service Instance is being processed by some other operation and therefore cannot be deleted at this time. The response body MUST contain error code "ConcurrencyError"
```
@pivotal-marcela-campo pivotal-marcela-campo merged commit be10eeb into main Oct 16, 2025
7 checks passed
@pivotal-marcela-campo pivotal-marcela-campo deleted the delcre branch October 16, 2025 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants