[
https://issues.apache.org/jira/browse/LIBCLOUD-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750232#comment-13750232
]
Michael Bennett commented on LIBCLOUD-383:
------------------------------------------
I took a stab at it using the "_ex_connection_class_kwargs" method you
suggested. Functionality appears to work as expected (from manual testing). I
added an ElasticHostsException class for the case where an invalid region is
specified or no region is specified (I think having it default to us-1 isn't
useful since people would need to look at source code to find out if it's
connecting to the datacenter they have credentials for or not).
Here's my working branch if you care to take a look and provide feedback.
Things that still need to be done are documenting the region kwarg, removing
the DEFAULT_ENDPOINT variable, and adding some test cases.
https://github.com/SecurityCompass/libcloud/tree/unify_elastichosts_driver
> Elastichosts driver missing us-3 api endpoint classes
> -----------------------------------------------------
>
> Key: LIBCLOUD-383
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-383
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Michael Bennett
> Priority: Trivial
> Fix For: 0.12.3
>
>
> The elastichosts driver is missing a NodeDriver and Connection class for the
> us-3 api endpoint (meta-data is present however). It is also missing and
> entry in libcloud.compute.types.Provider and
> libcloud.compute.providers.DRIVERS
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
