ASF GitHub Bot commented on NIFI-4199:

Github user jvwing commented on a diff in the pull request:

    --- Diff: 
    @@ -311,5 +312,10 @@ public void testGetPropertyDescriptors() throws 
Exception {
    +        assertTrue(pd.contains(ListS3.PROXY_HOST));
    --- End diff --
    Minor tweak: The check for PROXY_HOST and PROXY_HOST_PORT duplicates checks 
above on lines 309-310.  I believe this is why we add 5 lines of new 
assertions, but the count of property descriptors only goes up by 3 from 17 to 
20.  It doesn't make any difference, really, but the math was bothering me.

> NiFi processors should be able to share proxy settings
> ------------------------------------------------------
>                 Key: NIFI-4199
>                 URL: https://issues.apache.org/jira/browse/NIFI-4199
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Andre F de Miranda
>            Assignee: Koji Kawamura
>            Priority: Major
> Currently, configuring proxy settings for NiFi processors may be a tedious 
> process that requires the DFM to set proxy settings on individual processors. 
> This leads to:
> * Duplication of work
> * Management overhead (as password must be changed on multiple locations)
> * Lower security (as proxy credentials must be known by "n" DFMs)
> Ideally, NiFi should offer a way to minimise duplication of work by offering 
> a something similar to the Standard SSL Context services. This way, the DFM 
> could set the proxy settings once an all authorised users could tap into 
> those settings.

This message was sent by Atlassian JIRA

Reply via email to