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

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

GitHub user scottyaslan opened a pull request:

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

    [NIFI-2649] Update CS table upon creation of a CS from the RT propert…

    …ies table

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

    $ git pull https://github.com/scottyaslan/nifi devBranch

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

    https://github.com/apache/nifi/pull/968.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 #968
    
----
commit a6a9f9eb55555dc3722092ebf01bc2ede79f15a2
Author: Scott Aslan <[email protected]>
Date:   2016-08-29T21:47:52Z

    [NIFI-2649] Update CS table upon creation of a CS from the RT properties 
table

----


> Controller Services need to be refreshed when creating one inline from a 
> Reporting Task
> ---------------------------------------------------------------------------------------
>
>                 Key: NIFI-2649
>                 URL: https://issues.apache.org/jira/browse/NIFI-2649
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>            Reporter: Jeff Storck
>            Assignee: Scott Aslan
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> When configuring a Reporting Task such as SiteToSiteProvenanceReportingTask, 
> after creating a new SSLContextService inline in the property editor, if the 
> user hits the cancel button on the reporting tasks properties dialog, and 
> then clicks on the ControllerServices tab, the controller service isn't 
> listed.  Hitting refresh manually reveals the newly-created controller 
> service, or closing the NiFi Settings dialog and reopening it also reveals 
> the new controller service.



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

Reply via email to