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

ASF GitHub Bot commented on NIFI-2402:
--------------------------------------

GitHub user mcgilman opened a pull request:

    https://github.com/apache/nifi/pull/750

    Removing client side check for component move eligibility

    NIFI-2402:
    - Removing client side check component move eligibility and instead 
relaying on verification server side. Cannot check client side as the current 
user may not have permissions to inspect required fields.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mcgilman/nifi PR-2402

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/750.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #750
    
----
commit 48d29a38f128bbcafac0dcb742681efacedf1309
Author: Matt Gilman <[email protected]>
Date:   2016-07-29T21:45:41Z

    NIFI-2402:
    - Removing client side check component move eligibility and instead 
relaying on verification server side. Cannot check client side as the current 
user may not have permissions to inspect required fields.

----


> UI - Update logic to verify if components are eligible for moving
> -----------------------------------------------------------------
>
>                 Key: NIFI-2402
>                 URL: https://issues.apache.org/jira/browse/NIFI-2402
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>            Reporter: Matt Gilman
>            Assignee: Matt Gilman
>             Fix For: 1.0.0
>
>
> The logic to check if components are eligible for moving is still outdated. 
> Need to update to invoke the refactored endpoints or remove the client side 
> check entirely and perform the strictly server side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to