You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2013/11/28 11:19:42 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 ]
Tomaz Muraus updated LIBCLOUD-399:
----------------------------------
Fix Version/s: 0.14.0-beta3
> 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
> Assignee: Tomaz Muraus
> Fix For: 0.14.0-beta3
>
> Attachments: LIBCLOUD-399_20130915.diff, LIBCLOUD-399_20130915_1.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 was sent by Atlassian JIRA
(v6.1#6144)