Cannot bind to a service that only supports async binding create

[richard-cox]

• Related to Create Service Instance Stepper: Bind to app fails for async SI's #4161 (binding fails because service instance create is async) and V3 API: Support removal of sync service operations #3682 (v3 api removes support for sync service operations)
• We may need to look at this before the ever expected v3 release
• Raised by Comcast and required an impact-full workaround

[gberche-orange]

Observed symptom in stratos 4.4.0-defcc460f-cap when trying to create and bind an async service:

Failed to create service instance binding: An operation for service instance noop-from-stratos is in progress.. Code: CF-AsyncServiceInstanceOperationInProgress

[Rotfuks]

Hey folks!
I'm running into the same issue currently. Is there anything new to know about it?

My idea to get around the issue of the service-binding throwing errors because the async creation is not yet done is a bit "bigger". I'm not that sure that the Service Instance Creation and Binding in one process is an ideal situation to begin with. Sure it's a process you usually do one after another - but first step I'd rather go into the marketplace, select one service to create the service instance and then go directly to the app to bind it. Having to go through the service creation process more or less again...I'm not that sure I like that much.

So I think we could catch two birds with one stone by splitting up the workflows of service instance creation and service binding completely, having in the app overview just the option for binding and in the marketplace the option for instance creation. What do you folks think about that?