You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2019/07/29 06:32:05 UTC

[jira] [Closed] (OAK-8438) Allow not to create blob container in AzureDataStore

     [ https://issues.apache.org/jira/browse/OAK-8438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke closed OAK-8438.
-------------------------------

> Allow not to create blob container in AzureDataStore
> ----------------------------------------------------
>
>                 Key: OAK-8438
>                 URL: https://issues.apache.org/jira/browse/OAK-8438
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: blob-cloud-azure
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>            Priority: Major
>             Fix For: 1.16.0
>
>         Attachments: OAK-8438.patch
>
>
> When the SAS token is used for the AzureDataStore, it can be a container service SAS, which does allow to access the blobs, but doesn't allow to access the container itself. For instance, the {{CloudBlobContainer#exists()}} method throws a 403 error. This method is called by the {{createIfNotExists()}} in the {{AzureBlobStoreBackend#init}} method. As a result, the container SAS can't be used with the AzureBlobStore.
> Maybe we can create an extra config property, like {{azureCreateContainer}}, default true? If it's false, we can skip the {{createIfNotExists()}} invocation.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)