The juju GCE error message references the wrong key name

[Matt Bruzek]

When I am bootstrapping GCE I got an error message:

$ juju bootstrap google google
ERROR invalid config: project-id: must not be empty

So I added "project-id" to the json file. I still got the error. All the other keys in the json file used underscores "_" for word separation. I changed the key to "project_id" and bootstrap progressed further.

We should change the error message to give the user the proper key name "project_id" and maybe where to put it.

[Cheryl Jennings (cherylj)]

Marking as high as this is a usability issue.

[Tim McNamara (tim-clicks)]

This appears to have been fixed. Can longer replicate the bug. Here is a bash transcript:

$ juju add-credential google -f credentials.yaml
Credentials "credentials" added for cloud "google"

$ juju bootstrap google google
Creating Juju controller "google" on google/us-east1
Looking for packaged Juju agent version 2.5-beta2 for amd64
No packaged binary found, preparing local Juju agent binary
Launching controller instance(s) on google/us-east1...
Installing Juju agent on bootstrap instance
Fetching Juju GUI 2.14.0
Waiting for address
Attempting to connect to 35.231.176.23:22
Attempting to connect to 10.240.0.2:22
Connected to 35.231.176.23
Running machine configuration script...
Bootstrap agent now started
Contacting Juju controller at 35.231.176.23 to verify accessibility...
Bootstrap complete, "google" controller now available
Controller machines are in the "controller" model
Initial model "default" added