You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joey Frazee (Jira)" <ji...@apache.org> on 2020/09/16 21:39:00 UTC
[jira] [Commented] (NIFI-7794) PutAzureBlobStorage doesn't work
without permission to list containers
[ https://issues.apache.org/jira/browse/NIFI-7794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197247#comment-17197247 ]
Joey Frazee commented on NIFI-7794:
-----------------------------------
Paul, I think the spirit of the original change was to make it simpler which makes me think (1). My question if it's (2) would be is it a common use case to just create the container without any follow on writing to it?
> PutAzureBlobStorage doesn't work without permission to list containers
> ----------------------------------------------------------------------
>
> Key: NIFI-7794
> URL: https://issues.apache.org/jira/browse/NIFI-7794
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.12.0, 1.12.1
> Environment: All
> Reporter: Paul Kelly
> Priority: Major
> Labels: azureblob
>
> Due to the changes made for NIFI-6913, PutAzureBlobStorage no longer works without permission to list containers. This breaks some of our flows since we do not give permission to list containers to some of our users.
> Rather than checking that the container exists and trying to create it if it doesn't, one of these two methods seems like it might be better to automatically create containers since they can be done only when needed and permission is given:
> # Create a new boolean property for the PutAzureBlobStorage processor to determine if the container should be created if it doesn't exist. Only check to see if the container exists if this property is true.
> # Create a new processor named "CreateAzureBlobStorageContainer" and move the functionality for creating the container if it doesn't exist to this new processor.
> I'd be happy to contribute a pull request depending on what gets decided. I don't have a strong opinion either direction.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)