You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Olivier Grisel (JIRA)" <ji...@apache.org> on 2013/09/15 18:17:52 UTC
[jira] [Updated] (LIBCLOUD-399) Creating instances of
AzureBlobsStorageDriver should not mutate the host attribute of
AzureBlobsConnection
[ https://issues.apache.org/jira/browse/LIBCLOUD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Grisel updated LIBCLOUD-399:
------------------------------------
Attachment: LIBCLOUD-399_20130915.diff
Here is a patch with a fix + test for this issue. The patch is also available on this branch of my github fork:
https://github.com/ogrisel/libcloud/compare/LIBCLOUD-399
There might be a cleaner way to do it but I don't see how without resorting to metaclass which I think would make the code even more complex.
> 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.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