Because our configs get combined with all of the configs in the sub layers,
let's keep all of our config names in the scalebot_* name space. This will
both avoid potential conflicts with configs in other layers, and also
highlight the scalebot-specific configs for the end user.
Also, add "private" to the name so it is obvious that this isn't the
public key.
Finally, the git repository shouldn't have to be on Launchpad, so drop
the "lp" bit. Note that the charm currently only preloads the server host
keys for Launchpad into the jenkins user's known_hosts file. To really
support non-LP-git+ssh repos, we'd need to add a new config to pass in
arbitrary host keys, or maybe a "Trust On First Use" mode.
An ssh key is only needed when your scalebot config repo has a git+ssh://
URI. If you're accessing a public repo anonymously (git://), you should
be able to leave this empty.
proof: W: config.yaml: option scalebot_juju_bootstrap_constraints does not have the keys: default
proof: W: config.yaml: option scalebot_repo does not have the keys: default
proof: W: config.yaml: option scalebot_juju_model_defaults does not have the keys: default
proof: W: config.yaml: option scalebot_juju_credentials does not have the keys: default
proof: W: config.yaml: option lp_ssh_key does not have the keys: default
proof: W: config.yaml: option scalebot_juju_clouds does not have the keys: default
proof: W: config.yaml: option scalebot_branch does not have the keys: default