GCE provider is very restrictive when using a config-file (json)

[Charles Butler]

When i added the GCE provider and created a service account, the juju GCE provider forced me to remove ~ 6 keys from my config.json. This is problematic.

I feel that the juju config scanner should only care that we have the 4 required keys, the rest should simply be ignored.

The error messaging around this could be more helpful too:

ERROR there was an issue examining the environment: invalid config: key "auth_uri" not supported
ERROR there was an issue examining the environment: invalid config: key "project_id" not supported

This was the output from 1.26-alpha3-trusty-amd64

[Peter Matulis (petermatulis)]

I can confirm that when using the pointing method (auth-file) the following parts need to be removed from the auth file:

project-id
auth-uri
token_uri
auth_provider_x509_cert_url
client-x509-cert-url

Performing a character substitution ( s/_/-/ ) seems to help at first but ultimately the modified keys are rejected. The above keys are the unmodified (original) versions.

Using 2.0-alpha1-0ubuntu1~15.10.1~juju1 on Ubuntu 15.10.

[John A Meinel (jameinel)]

Using juju-2.0-beta8 (current master) this seems to be fixed. I can't confirm if it needs fixing for 1.25 series and/or 2.0-beta7, but I did not need to edit the file at all for this test.