GitHub user crunk1 opened a pull request:

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

    Google Storage permissions and libcloud.common.types.OrderedEnum

    - Added ex_(get|set|delete)_permissions to 
libcloud.storage.drivers.google_storage.GoogleStorageDriver
    - Added libcloud.common.types.OrderedEnum
    - Added tests for both of the above points.
    - Added a JSON connection to the GoogleStorageDriver. The JSON connection 
is only used in the new methods I added.
    - Performed manual tests to verify Google Storage permissions logic.
    - Minor cleanup: moved LazyObject to libcloud.common.types.LazyObject from 
libcloud.common.base.LazyObject
    - Minor cleanup: some python style changes to google_storage.py and 
test_google_storage.py.

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

    $ git pull https://github.com/crunk1/libcloud trunk

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

    https://github.com/apache/libcloud/pull/860.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 #860
    
----
commit 34c132869d499be422b83c91c46d030532c3d85e
Author: Scott Crunkleton <cru...@gmail.com>
Date:   2016-09-13T16:53:06Z

    Google Storage permissions support and libcloud.common.types.OrderedEnum.
    
    - Added ex_(get|set|delete)_permissions to 
libcloud.storage.drivers.google_storage.GoogleStorageDriver
    - Added libcloud.common.types.OrderedEnum
    - Added tests for both of the above points.
    - Added a JSON connection to the GoogleStorageDriver. The JSON connection 
is only used in the new methods I added.
    - Performed manual tests to verify Google Storage permissions logic.
    - Minor cleanup: moved LazyObject to libcloud.common.types.LazyObject from 
libcloud.common.base.LazyObject

----


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

Reply via email to