...alSupplier
This is WIP branch with an idea of how to move towards using JSON key files
instead of PEM keys.
Something along the lines of the following:
```
ComputeServiceContext context =
ContextBuilder.newBuilder("google-compute-engine")
.credentialsSupplier(new
GoogleComputeEngineCredentialSupplier("/path/to/file.json))
.buildView(ComputeServiceContext.class);
```
This also (optionally) changes how the live tests are run.
If you set the parameter `test.google-compute-engine.json-key` to
/path/to/file.json it will populate
`test.google-compute-engine.identity` and
`test.google-compute-engine.credential` from the file.
This will also require documentation updates ect.
@nacx WDYT?
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-google/pull/124
-- Commit Summary --
* Enables working with .json key files, adding
GoogleComputeEngineCredentialSupplier
-- File Changes --
A
google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/GoogleComputeEngineCredentialSupplier.java
(73)
M
google-compute-engine/src/test/java/org/jclouds/googlecomputeengine/compute/GoogleComputeEngineServiceLiveTest.java
(18)
M
google-compute-engine/src/test/java/org/jclouds/googlecomputeengine/internal/BaseGoogleComputeEngineApiLiveTest.java
(2)
-- Patch Links --
https://github.com/jclouds/jclouds-labs-google/pull/124.patch
https://github.com/jclouds/jclouds-labs-google/pull/124.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/124
