You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Eric Secules (Jira)" <ji...@apache.org> on 2021/02/05 23:55:00 UTC

[jira] [Commented] (NIFI-7386) AzureStorageCredentialsControllerService should also connect to storage emulator

    [ https://issues.apache.org/jira/browse/NIFI-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280042#comment-17280042 ] 

Eric Secules commented on NIFI-7386:
------------------------------------

Can we close this ticket as done? I see these changes have been included in the main branch.

> AzureStorageCredentialsControllerService should also connect to storage emulator
> --------------------------------------------------------------------------------
>
>                 Key: NIFI-7386
>                 URL: https://issues.apache.org/jira/browse/NIFI-7386
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Eric Secules
>            Assignee: Seokwon Yang
>            Priority: Major
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> The controller service "AzureStorageCredentialsControllerService" should be able to take an optional parameter to connect to another azure storage provider, like the [Azurite emulator|https://hub.docker.com/_/microsoft-azure-storage-azurite]. This will likely mean taking additional parameters for a base URL and possibly switching between http and https depending on Azurite's capabilities.
> I am currently setting up an isolated test environment for my application and the only piece that I cannot effectively isolate is our azure storage connection because NiFi doesn't support connecting to anything but the official azure storage service.
> *Acceptance Criteria:*
>  * AzureStorageCredentialsControllerService can connect to an alternative azure storage provider
>  * Individual azure storage processors can connect to an alternative azure storage provider
>  * New parameters will be optional and default to existing behaviour.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)