This pull request simplifies how instance credentials are managed: If no credentials are explicitly configured, jclouds will create an SSH key pair to access and bootstrap the instances (this can be controlled by the `autoCreateKeyPair` option in the `GoogleComputeEngineTemplateOptions`). If users provide their own access configuration in the template options, jclouds will just use those.
All ComputeService live tests are now passing. /cc @danbroudy You can merge this Pull Request by running: git pull https://github.com/nacx/jclouds-labs-google compute-auth Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-labs-google/pull/118 -- Commit Summary -- * Cleanup node authentication -- File Changes -- M google-compute-engine/README.md (2) M google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/compute/GoogleComputeEngineServiceAdapter.java (75) M google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/compute/config/GoogleComputeEngineServiceContextModule.java (9) M google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/compute/options/GoogleComputeEngineTemplateOptions.java (23) M google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/compute/strategy/CreateNodesWithGroupEncodedIntoNameThenAddToSet.java (103) D google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/compute/strategy/PopulateDefaultLoginCredentialsForImageStrategy.java (69) D google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/compute/strategy/UseNodeCredentialsButOverrideFromTemplate.java (57) M google-compute-engine/src/test/java/org/jclouds/googlecomputeengine/compute/GoogleComputeEngineServiceMockTest.java (3) -- Patch Links -- https://github.com/jclouds/jclouds-labs-google/pull/118.patch https://github.com/jclouds/jclouds-labs-google/pull/118.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/118
