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

Minor issue specifying external bosh director #46

Open
a2geek opened this issue Jul 25, 2021 · 0 comments
Open

Minor issue specifying external bosh director #46

a2geek opened this issue Jul 25, 2021 · 0 comments

Comments

@a2geek
Copy link

a2geek commented Jul 25, 2021

This is simple to overcome, but the external BOSH director needs more than the suggested configuration. When I only added the configuration:

  external_bosh:
    address:  (( vault "secret/exodus/" params.env "/bosh:url"))
    cacert:   (( vault "secret/exodus/" params.env "/bosh:ca_cert"))
    username: (( vault "secret/exodus/" params.env "/bosh:admin_username"))
    password: (( vault "secret/exodus/" params.env "/bosh:admin_password"))

I get the following error:

STDOUT:
2 error(s) detected:
 - $.meta.external_bosh_password: secret /secret/exodus/gdc-prod/bosh:blacksmith_password not found
 - $.meta.external_bosh_username: secret /secret/exodus/gdc-prod/bosh:blacksmith_user not found

Looking at external-bosh.yml, I noted the meta references which look for a different name. On a hunch, I tried this:

meta:
  external_bosh_password: NOT PRESENT
  external_bosh_username: NOT PRESENT

and that works. The text never makes it into the manifest, so it is functional...

Is there some more natural method to bypass this hack?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant