GitHub user erjohnso opened a pull request:

    https://github.com/apache/libcloud/pull/372

    LIBCLOUD-578: GCE adding Service Accounts to create_node

    Adding support for user-defined Service Account scopes when creating nodes 
in the GCE driver.  The default for this new paramter is modeled after both the 
Google Developers Console and Cloud SDK and sets an instance's (node's) default 
serviceAccount to,
    
    ```
    [{'email': 'default',
    'scopes': ['https://www.googleapis.com/auth/devstorage.read_only']
    }]
    ```
    
    To better match Google tools, short-name aliases as documented in Cloud 
SDK's `gcloud compute instances create --help` are supported.
    
    Typical usage would likely just use the 'default' email for the Service 
Account but allow overriding the list of scopes.  For example,
    
    ```
    ex_service_accounts = [{'scopes': ['bigquery','compute-ro', 'pubsub']}]
    ```
    
    Will map to,
    
    ```
    [{'email': 'default',
    'scopes': [
      'https://www.googleapis.com/auth/bigquery',
      'https://www.googleapis.com/auth/compute.readonly',
      'https://www.googleapis.com/auth/pubsub'
      ]
    }]
    ```
    
    GCE public docs on this capability are,
    https://cloud.google.com/compute/docs/authentication
    https://cloud.google.com/compute/docs/reference/latest/instances#resource
    
    
    /cc @ross-p


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/erjohnso/libcloud 
LIBCLOUD-578_gce_service_accounts

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/libcloud/pull/372.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #372
    
----
commit 1063f711e33caa854a61a0c44984cfac12e10cf8
Author: Eric Johnson <[email protected]>
Date:   2014-10-10T15:52:02Z

    LIBCLOUD-578: GCE adding Service Accounts to create_node

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to