sjyang18 commented on a change in pull request #4265:
URL: https://github.com/apache/nifi/pull/4265#discussion_r426940750



##########
File path: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/storage/utils/AzureStorageUtils.java
##########
@@ -85,6 +85,22 @@
             .sensitive(true)
             .build();
 
+    public static final PropertyDescriptor ENDPOINT_SUFFIX = new 
PropertyDescriptor.Builder()
+            .name("storage-endpoint-suffix")
+            .displayName("Storage Endpoint Suffix")
+            .description(
+                    "Storage accounts in public Azure always use a common FQDN 
suffix. " +
+                    "Override this endpoint suffix with a different suffix in 
certain circumsances (like Azure Stack or non-public Azure regions). " +
+                    "The preferred way is to configure them through a 
controller service specified in the Storage Credentials property. " +
+                    "The controller service can provide a common/shared 
configuration for multiple/all Azure processors. Furthermore, the credentials " 
+
+                    "can also be looked up dynamically with the 'Lookup' 
version of the service.")
+            .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)

Review comment:
       Given 
https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string#specify-an-http-proxy,
 the property for NIFI-7386 would be 'DevelopmentStorageProxyUri' or 
'development-storage-proxy-uri' in my opinion and we should call the correct 
API in this case(i.e. CloudStorageAccount.getDevelopmentStorageAccount(final 
URI proxyUri)).
   
   And, "EndPointSuffix" is one of connection property showing in Azure portal, 
and thus this is the obvious configuration in non public Azure cloud 
environemnt.
   




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to