You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2016/04/28 15:15:12 UTC

[jira] [Resolved] (JCLOUDS-1043) Google IAM release breaks GoogleComputeEngineHttpApiModule

     [ https://issues.apache.org/jira/browse/JCLOUDS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ignasi Barrera resolved JCLOUDS-1043.
-------------------------------------
    Resolution: Fixed

> 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)