Operate on component policy

[Dan Caulfield <da...@gm.com>]

We are setting up a user/group policy to allow an operations team to start/stop processors and process groups.  The operate component works fine at the process group level but does not inherit to the processors.  Even explicitly assigning the operate policy one the processor does not allow the user to start/stop the processor.

Has anyone else tried setting the operate component to control an individual process?
[cid:image001.png@01D5790A.1357E960]






Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.

Re: Operate on component policy

[Matt Gilman <ma...@gmail.com>]

Thanks for reporting this Dan. I have captured the issue in this JIRA [1].

[1] https://issues.apache.org/jira/browse/NIFI-6845

On Wed, Oct 2, 2019 at 5:15 PM Dan Caulfield <da...@gm.com> wrote:

> Found the issue. The operate palette does reflect the correct operate
> actions when the processor is selected. Right clicking the processor
> results in the correct behavior.
>
>
>
> *From:* Dan Caulfield <da...@gm.com>
> *Sent:* Wednesday, October 02, 2019 10:14 AM
> *To:* users@nifi.apache.org
> *Subject:* [EXTERNAL] Operate on component policy
>
>
>
> We are setting up a user/group policy to allow an operations team to
> start/stop processors and process groups.  The operate component works fine
> at the process group level but does not inherit to the processors.  Even
> explicitly assigning the operate policy one the processor does not allow
> the user to start/stop the processor.
>
>
>
> Has anyone else tried setting the operate component to control an
> individual process?
>
>
>
>
>
>
>
>
>
>
>
> Nothing in this message is intended to constitute an electronic signature
> unless a specific statement to the contrary is included in this message.
>
> Confidentiality Note: This message is intended only for the person or
> entity to which it is addressed. It may contain confidential and/or
> privileged material. Any review, transmission, dissemination or other use,
> or taking of any action in reliance upon this message by persons or
> entities other than the intended recipient is prohibited and may be
> unlawful. If you received this message in error, please contact the sender
> and delete it from your computer.
>
>
> Nothing in this message is intended to constitute an electronic signature
> unless a specific statement to the contrary is included in this message.
>
> Confidentiality Note: This message is intended only for the person or
> entity to which it is addressed. It may contain confidential and/or
> privileged material. Any review, transmission, dissemination or other use,
> or taking of any action in reliance upon this message by persons or
> entities other than the intended recipient is prohibited and may be
> unlawful. If you received this message in error, please contact the sender
> and delete it from your computer.
>

RE: Operate on component policy

[Dan Caulfield <da...@gm.com>]

Found the issue. The operate palette does reflect the correct operate actions when the processor is selected. Right clicking the processor results in the correct behavior.

From: Dan Caulfield <da...@gm.com>
Sent: Wednesday, October 02, 2019 10:14 AM
To: users@nifi.apache.org
Subject: [EXTERNAL] Operate on component policy

We are setting up a user/group policy to allow an operations team to start/stop processors and process groups.  The operate component works fine at the process group level but does not inherit to the processors.  Even explicitly assigning the operate policy one the processor does not allow the user to start/stop the processor.

Has anyone else tried setting the operate component to control an individual process?

[cid:image001.png@01D5793A.337AAF40]





Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.


Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.