You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by erjohnso <gi...@git.apache.org> on 2014/12/30 22:13:04 UTC

[GitHub] libcloud pull request: [LIBCLOUD-610] gce: better error message fo...

GitHub user erjohnso opened a pull request:

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

    [LIBCLOUD-610] gce: better error message for missing key file

    This small fix addresses feedback in https://issues.apache.org/jira/browse/LIBCLOUD-610. A check is introduced for the existence and readability of the private key file before passing it on to pycrypto.  If the check fails, the user is notified that the private key file is not present or readable.

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

    $ git pull https://github.com/erjohnso/libcloud LIBCLOUD-610_gce_keyfile_check

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

    https://github.com/apache/libcloud/pull/424.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 #424
    
----
commit 7803f349aa88ab4fc3048941c70af9d1c9903b0c
Author: Eric Johnson <er...@google.com>
Date:   2014-12-30T21:10:41Z

    [google compute] better error message for missing key file

----


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

[GitHub] libcloud pull request: [LIBCLOUD-610] gce: better error message fo...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


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