Skip to content

Minor issue specifying external bosh director #46

@a2geek

Description

@a2geek

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions