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 "Amit Jain (JIRA)" <ji...@apache.org> on 2017/10/13 10:43:00 UTC

[jira] [Resolved] (OAK-6802) Manage 'secret' property internally in S3/AzureDataStore

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

Amit Jain resolved OAK-6802.
----------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.10

Closing streams and re-reading the created content to ensure the object key actually assigned used
S3 - http://svn.apache.org/viewvc?rev=1812109&view=rev
Azure - http://svn.apache.org/viewvc?rev=18121010&view=rev

> Manage 'secret' property internally in S3/AzureDataStore
> --------------------------------------------------------
>
>                 Key: OAK-6802
>                 URL: https://issues.apache.org/jira/browse/OAK-6802
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: blob-cloud, blob-cloud-azure
>            Reporter: Amit Jain
>            Assignee: Amit Jain
>             Fix For: 1.8, 1.7.10
>
>
> Property 'secret' is required to be configured (which is a shared secret among instances sharing the datastore) to enable binary-less replication. The DataStore should manage it internally as it does for other things in the META folder like in the container like repository ID etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)