libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sayoun <...@git.apache.org>
Subject [GitHub] libcloud pull request #1065: [LIBCLOUD-917] Gandi compute driver should use ...
Date Tue, 30 May 2017 10:22:36 GMT
GitHub user sayoun opened a pull request:

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

    [LIBCLOUD-917] Gandi compute driver should use a unique location name

    ### Description
    
    Gandi compute driver uses a non unique field value as name for locations
    
    See JIRA ticket https://issues.apache.org/jira/browse/LIBCLOUD-917
    
    ### 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)
    - [ ] 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/Gandi/libcloud LIBCLOUD-917_gandi_unique_location_name

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

    https://github.com/apache/libcloud/pull/1065.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 #1065
    
----
commit ff021f7d0e0180ccd09629e5c9372f72e7209a26
Author: sayoun <sayoun@gandi.net>
Date:   2017-05-30T10:17:23Z

    [LIBCLOUD-917] Gandi compute driver should use a unique location name

----


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