[
https://issues.apache.org/jira/browse/JCLOUDS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262110#comment-15262110
]
ASF subversion and git services commented on JCLOUDS-1043:
----------------------------------------------------------
Commit 3053cb5ae2df54150c44bb4476370c7f34495b5e in jclouds-labs-google's branch
refs/heads/1.9.x from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-google.git;h=3053cb5 ]
JCLOUDS-1043: Support IAM service accounts in Google Cloud
> Google IAM release breaks GoogleComputeEngineHttpApiModule
> ----------------------------------------------------------
>
> Key: JCLOUDS-1043
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1043
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.9.1
> Environment: Google Compute Engine + JClouds
> Reporter: Nelson Araujo
> Priority: Minor
> Labels: google-compute-engine
> Fix For: 2.0.0
>
>
> JClouds relies on parsing the service account email address to extract the
> Project ID from it. With the upgrade of Google Compute Engine to integrate
> with Cloud IAM (https://cloud.google.com/iam) the user is in control of the
> service account name.
> Without the project ID fixed at the beginning of the account email JClouds
> fails to identify the project and all requests fail.
> Problem happens in
> org.jclouds.googlecomputeengine.config.GoogleComputeEngineHttpApiModule:
> @Provides @UserProject Supplier<String> supplyProject()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
