libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From erjohnso <...@git.apache.org>
Subject [GitHub] libcloud pull request: LIBCLOUD-625: Allow for internal GCE author...
Date Sat, 18 Oct 2014 02:47:04 GMT
GitHub user erjohnso opened a pull request:

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

    LIBCLOUD-625: Allow for internal GCE authorization with metadata service

    This PR provides support for authorizing requests from within GCE directly by pulling
an authorization token out of GCE's internal metadata services.  This greatly simplifies using
libcloud inside GCE since it does not require the user to copy around private auth files.
 The only parameter required for this method is the user's Project ID.  See the included docs
for a sample use-case.
    
    This PR also attempts to address https://issues.apache.org/jira/browse/LIBCLOUD-607 by
appending the Project ID to the cached credential file.

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

    $ git pull https://github.com/erjohnso/libcloud LIBCLOUD-625_gce_auth_internal

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

    https://github.com/apache/libcloud/pull/376.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 #376
    
----
commit 0e024f4759f558483340d9548cff827052fc803f
Author: Eric Johnson <erjohnso@google.com>
Date:   2014-10-18T02:17:00Z

    LIBCLOUD-625: Allow for internal GCE authorization with metadata service

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message