CF push with manifest does not honor the order of service bindings

[madevr]

Hi,

Using most recent CF CLI version.

The order of the service bindings in a manifest is not honored when doing a cf push.

For example:
I have an app that needs to be bound to serviceA and serviceB. serviceB requires that serviceA is already bound, and it also checks this when the binding to it happens. Therefore, I define the following service bindings in my manifest:

• serviceA
• serviceB

I expect that first, serviceA is bound, and then serviceB is bound to my app.

However, when executing cf push, it can happen that serviceB is bound first, resulting in an error.

Would it be possible to honor the order of the services? Or to provide an option for this?

Thanks and kind regards

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/156910907

The labels on this github issue will be updated when the story is started.

[XenoPhex]

We can look into this, but it's possible our yaml library is reading them out of order. If that is the case, there's not much we can do.