Hi,
Thanks!! As suggested would go for a new module oak-blob-cloud-azure.
Regards
Amit
On Thu, Mar 16, 2017 at 9:50 PM, Angela Schreiber wrote:
> Hi Amit
>
> In the light of discussions we had recently wrt modularisation, I would
> also prefer to keep the new
Hi Amit
In the light of discussions we had recently wrt modularisation, I would
also prefer to keep the new oak-blob-cloud-azure implementation in a
separate module.
Kind regards
Angela
On 15/03/17 10:29, "Amit Jain" wrote:
>Hi Team,
>
>There is a new contribution for azure
On 15/03/2017 09:29, Amit Jain wrote:
> Hi Team,
>
> There is a new contribution for azure blob storage support - OAK-4933.
> This introduces a new module oak-blob-cloud-azure. This certainly seems to
> be the right approach from a separation and deployment standpoint. But in
> terms of code the
I tend to agree with Arek on this one. It feels a good logical division to
have it separate, primarily so when updates to the Azure SDK are released,
a new version of this module can be released without having to update
oak-blob-cloud. By that same argument it may make sense at some point to
do
Hi Amit,
On 15/03/2017, 10:29, "amit@gmail.com on behalf of Amit Jain"
wrote:
> Hi Team,
>
> There is a new contribution for azure blob storage support - OAK-4933.
> This introduces a new module oak-blob-cloud-azure. This certainly seems to
>