Support service-to-service bindings about servicebroker HOT 3 CLOSED

That PoC proposal seems to completely change the way the API currently work. How would we reconcile future instantiation with the current REST API? Would we have separate operations for create and instantiate?

Sounds like defining workflows, a more complex and refined use case of the API. I agree with @shalako that this functionality should be provided by a higher level component using the API as-is.

from servicebroker.

In order for bindings to be of any value, they must be able to model relationships between two service instances.

This strikes me as hyperbole. Does the K8 developer not have an application for which they are responsible? Despite not having an explicit service-to-service binding feature, the existing binding behavior has provided a great deal of value to CF end-users.

Service-to-service binding can currently be fulfilled in CF with a workaround using service keys and parameters. Developer wants to bind service 1 ("from") to service 2 ("to"). They would create a service key of service 2 ("to"). A service key is just a binding that isn't delivered to an app, and for which the developer can discover the details. They can then create/update service 1 ("from") with the data from service 2 in the parameters field. Seems to me a marketplace controller could orchestrate this flow without any change to the broker API.

The top-level app_guid field in the create-binding request should be considered a deprecated field, as we introduced bind_resource to support fields the broker expects from the marketplace controller. For this use-case, it seems to me parameters is more appropriate. A broker may or may not support configuration of a service instance that grants it access to another service.

from servicebroker.

This issue was created when the repo was geared toward both an open broker and controller spec. I agree that this is more of a controller feature, and does not strictly necessitate broker API changes to function (e.g., can use existing parameters field).

from servicebroker.