[ https://issues.apache.org/jira/browse/NIFI-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434513#comment-16434513 ]
ASF GitHub Bot commented on NIFI-4997: -------------------------------------- Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/2626 @mcgilman thanks, this definitely simplifies the code a lot, too, and makes it more consistent. Was able to verify starting/stopping process groups/individual components. Was able to verify changing to different versions of a versioned flow, and changing variable registry. All handled the authorization properly. Tested all of the above in both standalone mode and clustered. +1 will merge to master. > Actions taken on process groups do not appear in flow configuration history > --------------------------------------------------------------------------- > > Key: NIFI-4997 > URL: https://issues.apache.org/jira/browse/NIFI-4997 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI > Affects Versions: 1.4.0 > Environment: CentOS 7, Docker > Reporter: Craig Becker > Assignee: Matt Gilman > Priority: Major > > Selecting a process group and executing a stop or start action does not cause > anything to be logged in the flow configuration history. The current behavior > makes it impossible to trace who/when a process group was turned off. > > The expected/desired behavior would be to either add a log entry per > processor that was stopped/started, or to log that the process group was > stopped/started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)