[
https://issues.apache.org/jira/browse/LIBCLOUD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767924#comment-13767924
]
Tomaz Muraus commented on LIBCLOUD-399:
---------------------------------------
No problem.
I have fixed a typo and pushed another change to only return "host" in the
"_ex_connection_class_kwargs" method if the "host" argument is not passed to
the driver constructor
(https://git-wip-us.apache.org/repos/asf?p=libcloud.git;a=commitdiff;h=5888d45c000ba3045ba03cb845a8191a822409e6).
The reason is that "host" argument, if present, has precedence over "key".
This way users can, for example, also use it with other installations which
expose Azure API.
> Creating instances of AzureBlobsStorageDriver should not mutate the host
> attribute of AzureBlobsConnection
> -----------------------------------------------------------------------------------------------------------
>
> Key: LIBCLOUD-399
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-399
> Project: Libcloud
> Issue Type: Bug
> Components: Storage
> Affects Versions: 0.13.1
> Reporter: Olivier Grisel
> Attachments: LIBCLOUD-399_20130915_1.diff, LIBCLOUD-399_20130915.diff
>
>
> Creating instances of {{AzureBlobsStorageDriver}} should not mutate the
> {{host}} attribute of {{AzureBlobsConnection}}.
> The {{host}} attribute is dependent on the {{key}} of the azure blob storage
> account. It should be possible to have 2 drivers to do distinct Azure storage
> accounts in the same Python program without having one driver instance affect
> the state of another.
> Please followup for a patch.
--
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
