Possible Deprovision Bug

[jasonodonnell]

I think there might be a bug in the documentation for deprovision.

Deprovision doc states that the expected request should look like the following:

http://username:password@broker-url/v2/service_instances/:instance_id?service_id=service-id-here&plan_id=plan-id-here

However, a broker I wrote is failing on deprovision and the request I'm getting looks like this:

The service broker returned an invalid response for the request to http://10.244.4.5:8080/v2/service_instances/a65c39ab-32a9-4f74-8963-bacfbb0273c2. Status Code: 409 Conflict, Body: {}

Looking at the source code suggests a body should be returned.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/130698269

The labels on this github issue will be updated when the story is started.

[jasonodonnell]

My apologies, I was wrong, it seems the parameters were just being truncated for display. After tinkering a bit I was able to extract them.

[pspinrad]

No prob - FWIW, it looks like the broker was returning an unexpected status code, 409. Valid exit codes are 200, 202, and 410-- see docs https://docs.cloudfoundry.org/services/api.html#deprovisioning "Response" section.