Date 1 - 3 of 3
Service Broker API - updating instances
Shannon,toggle quoted message Show quoted text
The polling API in the the Asynchronous Operations documentation suffers
from the same problem. Perhaps the .../last_operation request could include
a service_id query parameter?
On Thu, Jun 11, 2015 at 5:33 PM, Shannon Coen <scoen(a)pivotal.io> wrote:
Hello Mike,toggle quoted message Show quoted text
Quite reasonable. I'll put a story in the backlog.
Product Manager, Cloud Foundry
On Thu, Jun 11, 2015 at 2:15 PM, Mike Heath <elcapo(a)gmail.com> wrote:
One of the really nice features of the V2 Service Broker API is the
One of the really nice features of the V2 Service Broker API is the ability
to broker multiple services from a single process. Each service provides
its unique id in the broker catalog. The Cloud Controller then includes
that unique id with requests to the broker making it easy for the broker to
route the request to the correct service.
The problem I'm currently having is that the API added in version 2.4 for
updating a service instances does not include the service's unique id .
It only provides the service instance's id and the new plan id. This makes
it very difficult to route the update request to the correct service
provider within a process brokering multiple services as it would require
querying each service provider to determine if it brokered the provided
I would like to propose adding a service_id field to the update request,
the same as every other request in the service broker API. I believe that
the main issue with this is that it implies that an instance's service
provider could be changed by the broker. I think proper documentation would
alleviate that issue though.
1 - http://docs.cloudfoundry.org/services/api.html#updating_service_instance
|1 - 3 of 3|