Gareth Clay

Support async service binding operations

1

The V2 service bindings API supports and `accepts_incomplete` query parameter ([create binding example](https://apidocs.cloudfoundry.org/13.2.0/service_bindings/create_a_service_binding.html)), which can be set to `true` by clients wanting to perform asynchronous service binding operations. It's not...

Update App Broker to use the [release notes generator](https://github.com/spring-io/github-release-notes-generator) used by other Spring projects. [Documentation](https://github.com/spring-projects/spring-boot/wiki/GitHub-Issues) [Docker image](https://hub.docker.com/r/springio/github-release-notes-generator)

Without a Target to disambiguate service instances, App Broker will deploy over the top of the existing instance on the second `cf create-service` attempt. Log when defaulting behaviour.

Reference documentation needs to be updated to cover the new logging endpoints and starter dependency.

Can App Broker provide more assistance around concurrency control?

2

We've hit a problem in our App Broker based broker when an unbind operation races with a service instance deletion. Our unbind involves an update of the SI backing app,...

``` 12-05-2021 17:18:14.731 [reactor-http-epoll-3] INFO o.s.c.a.a.f.cf.CloudFoundryService.lambda$deleteServiceBroker$23 - Success deleting service broker. brokerName=((redacted))-broker-update-instance 12-05-2021 17:18:15.055 [reactor-http-epoll-3] INFO o.s.c.a.a.f.cf.CloudFoundryService.lambda$deleteApp$18 - Success deleting app. appName=((redacted))-broker-app-update-instance 12-05-2021 17:18:25.126 [reactor-http-epoll-5] INFO o.s.c.a.a.f.cf.CloudFoundryService.lambda$deleteServiceBroker$23 - Success deleting...