[
https://issues.apache.org/jira/browse/NIFI-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620195#comment-16620195
]
ASF GitHub Bot commented on NIFI-375:
-------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/2990
@mcgilman Incorporated the last review comments.
The original intent of having `operatePermissions` at each concrete entity
implementation is to clarify which entity is `OperationPermissible`. I thought
adding that to ComponentEntity is to vague as ComponentEntity is the super
class of various entities, including those do not have running status such as
`AccessPolicySummaryEntity`, `TemplateEntity` or `UserGroupEntity`.
I wasn't consistent enough while I was refactoring the code at some point
and added it to ComponentEntity. But I still think the operatePermissions
should exist with only component those can be operated. So, I removed
operatePermissions from ComponentEntity.
I hope this we have polished this PR enough to get merged. Thanks for your
comprehensive review comments!
> New user role: Operator who can start and stop components
> ---------------------------------------------------------
>
> Key: NIFI-375
> URL: https://issues.apache.org/jira/browse/NIFI-375
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Reporter: Daniel Ueberfluss
> Assignee: Koji Kawamura
> Priority: Major
>
> Would like to have a user role that allows a user to stop/start processors
> but perform no other changes to the dataflow.
> This would allow users to address simple problems without providing full
> access to modifying a data flow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
