Re: [Proposal] Asynchronous service broker bindings
Dr Nic Williams <drnicwilliams@...>
That's a pity to hear that there a long binding requests in the world - I was recently pondering the idea of dynamically rebinding individual containers to service instances on each container restart. I'd never seen a long binding request so it seemed like a great opportunity to continuously rotate credentials (without user involvement).toggle quoted messageShow quoted text
On Mon, Mar 20, 2017 at 8:38 PM +1000, "Matthew McNeeney" <mmcneeney(a)pivotal.io> wrote:
The bind and unbind API calls to a service broker currently only support synchronous operations. This is causing problems for service brokers that have a long running workflow (such as provisioning new user accounts, setting up firewalls, etc) as the default 60 second CF timeout  can easily be exceeded. A proposal  has been drawn up that changes the specification  to additionally allow asynchronous binding and unbinding (similar to how asynchronous create, update and delete currently work). There is an outstanding Github issue  from the Open Service Broker API working group that contains more context on this.
We're also proposing that this is added to the CF CLI, with the same UX as create, update and delete.
Has anyone else faced issues with synchronous (un)binding timeouts?
Any feedback is welcome via the Github issue or this mail.
 https://github.com/cloudfoundry/cloud_controller_ng/blob/master/bosh/jobs/cloud_controller_ng/spec#L570 https://github.com/avade/servicebroker/blob/async-binding/spec.md#request-4
 https://github.com/avade/servicebroker/commit/497ecdaa7307dc05b0f4448c2d51bbe1dbe5a684 https://github.com/openservicebrokerapi/servicebroker/issues/137