Skip to content
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.

Check Bosh registry URI configuration consistency #37

Closed
f-guichard opened this issue Aug 10, 2016 · 2 comments
Closed

Check Bosh registry URI configuration consistency #37

f-guichard opened this issue Aug 10, 2016 · 2 comments
Milestone

Comments

@f-guichard
Copy link

All first bosh deployments has failed since bosh registry Basic Auth has been implemented, because of wrong endpoint specification in yaml file.

URI should be built from endpoint + user + password from bosh yaml deployment file.

@poblin-orange
Copy link
Member

basic-auth was added in cpi v11.
The change was clearly stated in the release note https://github.com/cloudfoundry-community/bosh-cloudstack-cpi-release/releases/tag/v11, in the "uncompatible change" section, with a manifest snippet. Hard to be more explicit ;-)

Agreed thats a bit redundant. However, this is the same on other CPI (openstack, vcloud, aws).

This redudancy enables use cases like AWS bosh-init through ssh tunnel, where bosh-registry is accessed with a http://127.0.0.1 address by the bosh agent.

Not sure there is enough value to diverge from the other CPIs

@poblin-orange poblin-orange changed the title Change Bosh registry URI building mechanism Check Bosh registry URI configuration consistency Aug 18, 2016
@poblin-orange
Copy link
Member

finally, a simple consistency check should match the requirement see PR cloudfoundry-community/bosh-cloudstack-cpi-core#5

@poblin-orange poblin-orange added this to the 13 milestone Sep 6, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants