Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
madevr opened this issue Apr 19, 2018 · 5 comments
Closed

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

madevr opened this issue Apr 19, 2018 · 5 comments
Labels
accepted contributions welcome Contributors are welcome to submit a pull request. Please read our Contributors Guide. enhancement sapi

Comments

@madevr
Copy link

madevr commented Apr 19, 2018

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
Copy link
Collaborator

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
Copy link
Contributor

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.

@abbyachau abbyachau added the contributions welcome Contributors are welcome to submit a pull request. Please read our Contributors Guide. label May 11, 2018
@abbyachau
Copy link
Contributor

hey @selzoc @ssisil do you know if this is still an issue using v3 server side manifests?

@selzoc
Copy link
Member

selzoc commented Aug 21, 2019

It looks like we do them in the order that they appear in the manifest using server side manifests.

@abbyachau
Copy link
Contributor

Hi @madevr it looks like this is no longer an issue on cf7 beta/v3 API (CAPI owns manifests in cf7). The cf7 beta is available here. Please let us know if you have any feedback, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted contributions welcome Contributors are welcome to submit a pull request. Please read our Contributors Guide. enhancement sapi
Projects
None yet
Development

No branches or pull requests

7 participants