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

Jump to bottom

Clarify how to clean-up during a failed provision/bind #353

Merged
merged 2 commits into from
Nov 7, 2017
Merged

Clarify how to clean-up during a failed provision/bind #353

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5dc442b
Clarify how to clean-up during a failed provision/bind
Oct 26, 2017
ebf6c39
add to more spots
Oct 31, 2017
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
12 changes: 10 additions & 2 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -718,6 +718,10 @@ For success responses, the following fields are valid.
}
```

If the successful response includes a `state` of `failed` then the Platform
MUST send a deprovision request to the Service Broker to prevent an orphan
being created on the Service Broker.

### Polling Interval and Duration

The frequency and maximum duration of polling MAY vary by platform client. If
Expand Down Expand Up @@ -817,7 +821,11 @@ $ curl http://username:password@service-broker-url/v2/service_instances/:instanc
| 409 Conflict | MUST be returned if a service instance with the same id already exists but with different attributes. The expected response body is `{}`, though the description field MAY be used to return a user-facing error message, as described in [Service Broker Errors](#service-broker-errors). |
| 422 Unprocessable Entity | MUST be returned if the Service Broker only supports asynchronous provisioning for the requested plan and the request did not include `?accepts_incomplete=true`. The expected response body is: `{ "error": "AsyncRequired", "description": "This service plan requires client support for asynchronous service operations." }`, as described below (see [Service Broker Errors](#service-broker-errors). |

Responses with any other status code will be interpreted as a failure. Service brokers can include a user-facing message in the `description` field; for details see [Service Broker Errors](#service-broker-errors).
Responses with any other status code will be interpreted as a failure and a
deprovision request MUST be sent to the Service Broker to prevent an orphan
being created on the Service Broker.
Service Brokers can include a user-facing message in the `description` field;
for details see [Service Broker Errors](#service-broker-errors).

#### Body

Expand Down Expand Up @@ -1155,7 +1163,7 @@ $ curl http://username:password@service-broker-url/v2/service_instances/:instanc
| 422 Unprocessable Entity | MUST be returned if the Service Broker requires that `app_guid` be included in the request body. The expected response body is: `{ "error": "RequiresApp", "description": "This service supports generation of credentials through binding an application only." }` (see [Service Broker Errors](#service-broker-errors). |

Responses with any other status code will be interpreted as a failure and an
unbind request will be sent to the Service Broker to prevent an orphan being
unbind request MUST be sent to the Service Broker to prevent an orphan being
created on the Service Broker. Service brokers can include a user-facing
message in the `description` field; for details see [Service Broker
Errors](#service-broker-errors).
Expand Down