libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From schaubl <...@git.apache.org>
Subject [GitHub] libcloud pull request: Fix openstack v3 authentication
Date Tue, 12 Apr 2016 21:17:38 GMT
GitHub user schaubl opened a pull request:

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

    Fix openstack v3 authentication

    ## Fix openstack v3 authentication
    
    ### Description
    
    This PR allows to define the OpenStack `domain` to another value that the default `Default`.
    It also adds the ability to define the `scope` of the token.
    
    With the code for the OpenStack Identity API v3, [two new parameters were added](https://github.com/apache/libcloud/blob/v0.20.1/libcloud/common/openstack_identity.py#L925):
`domain_name` and `token_scope` but it was impossible to define them to a value other than
their respective default.
    
    ### Status
    
    - done, ready for review
    
    ### Checklist (tick everything that applies)
    
    - [x] [Code linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
(required, can be done after the PR checks)
    - [x] Documentation
    - [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
    - [ ] ~~[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
(required for bigger changes)~~
    


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

    $ git pull https://github.com/schaubl/libcloud openstack-fix_auth_v3

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

    https://github.com/apache/libcloud/pull/744.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 #744
    
----
commit 777278ba9762b5a0e7bf4f56412602d1a092848d
Author: lionel <lionel@sixsq.com>
Date:   2016-04-12T20:58:16Z

    Fix openstack v3 authentication

----


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