CF push with manifest does not honor the order of service bindings #1367
Labels
accepted
contributions welcome
Contributors are welcome to submit a pull request. Please read our Contributors Guide.
enhancement
sapi
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:
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
The text was updated successfully, but these errors were encountered: