Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be clear about the state of resources after a failure #541

Merged
merged 1 commit into from
Jul 12, 2018
Merged

Be clear about the state of resources after a failure #541

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -294,6 +294,15 @@ use these error codes for the specified failure scenarios.
| ConcurrencyError | The Service Broker does not support concurrent requests that mutate the same resource. | Clients MUST wait until pending requests have completed for the specified resources. |
| RequiresApp | The request body is missing the `app_guid` field. | The `app_guid` MUST be included in the request body. |

Unless otherwise specified, an HTTP status code in the 4xx range MUST result in
the Service Broker's resources being semantically unchanged as a result of
the incoming request message. Additionally, an HTTP status code in the 5xx
range SHOULD result in the Service Broker's resources being semantically
unchanged as a result of the incoming request message. Note, the 5xx error
case is a "SHOULD" instead of a "MUST" because it might not be possible for
a Service Broker to guarantee that it can revert all possible effects of a
failed attempt at the requested operation.

### Content Type

All requests and responses defined in this specification with accompanying
Expand Down