-
Notifications
You must be signed in to change notification settings - Fork 36
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
Allow specifying port and databases for bbr when not using bosh links #46
Conversation
✅ Hey rkoster! The commit authors and yourself have already signed the CLA. |
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/162541460 The labels on this github issue will be updated when the story is started. |
@rkoster thank you very much for sending this PR. We would like to support the feature, but unfortunately we cannot accept it as is because it is missing an acceptance test. It should verify that a co-located bbr-postgres-db job without a link present can successfully back up and restore a database. |
252f0c4
to
d8dbdbe
Compare
@valeriap have added a test, it compiles but I'm unable to run test in my current environment. Apparently the test suite does not support bosh with uaa auth... |
@rkoster Thanks for updating the test suite.
With this typo fixed the suite has run fine. |
Thanks, have fixed the typo |
Since bosh create-env still does not support using links, I would like to propose the following changes to the bbr job. To allow us to switch to the postgres bbr job, for bucc.
Original issue: #26