Kent Rancourt

@fmui note that in our approach, we do not speak of "bindings" between instances. Conceptually, yes, that's what's going on, but we found it easier to socialize this idea internally...

@mattmcneeney > Question: If the same service broker is providing all of the services in this dependency change, then why does the broker need to expose this to the developer?...

@duglin I'd rather not rely on all platforms implementing that because unless they _all_ do, we couldn't guarantee that any of the above would work across platforms, so our broker...

> if the services are managed by different brokers... My examples involve services provided by a single broker that are explicitly designed to work together to enable the use cases...

@duglin I still think there needs to be a deep dive on this, but I think that you and I at least are converging on a common perspective on this.

@duglin do we know when that's happening. I want to be sure to have that on my calendar.

@vdice and I have discussed this and decided not to let this issue hold up beta.4 / rc.1 / GA. Due to the asynchronous nature of Brigade and a deliberate...

A closer look at the logs reveals that _three_ jobs appear not to have made it onto the queue, although they did. Two of them happened to succeed before the...

I have a suspicion about what's happening. Success or failure, these jobs do eventually finish. I suspect that some (unlogged) error is causing the finite number of goroutines that the...

Labeling this as an enhancement (as opposed to a bug) because, as you've noted, the fact that this ever worked the way it once did was a quirk and wasn't...