[
https://issues.apache.org/jira/browse/NIP-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18075477#comment-18075477
]
Kevin Doran commented on NIP-28:
--------------------------------
Thanks Mark. I am supporting of this NIP.
> Allow Connectors to have a 'Break Glass in Case of Emergency' Troubleshooting
> mode
> ----------------------------------------------------------------------------------
>
> Key: NIP-28
> URL: https://issues.apache.org/jira/browse/NIP-28
> Project: NiFi Improvement Proposal
> Issue Type: Improvement
> Reporter: Mark Payne
> Priority: Major
>
> h2. Motivation
> The design for Connectors (https://issues.apache.org/jira/browse/NIP-11) was
> that these are self-contained end-to-end abstractions. The Connector manages
> the flow by itself and while the user should be able to view the flow, they
> should not be able to modify it in any way, except configuring the Connector.
> While this makes sense, it also takes away the ability to troubleshoot in the
> way that we are used to with NiFi.
>
> h2. Proposed Solution
> The proposal is to allow for a 'Troubleshooting' mode for Connectors. In this
> mode, the Connector's flow will be modifiable. The user can go in and
> add/delete/update components. But they will not be able to Start, Stop, or
> update the configuration of the Connector itself.
> This allows for quickly addressing any issues that come up while the
> Connector is running. But we cannot have code that expects to manage the flow
> while at the same time allowing users to manipulate the flow. So this
> provides the ability to effectively switch between the flow being managed by
> the Connector and the flow being managed by the user.
> Once the user has resolved the issue, they can exit the Troubleshooting mode.
> At that point, the Connector will resume the responsibility of managing the
> flow, and the user will no longer be able to manipulate it. This means that
> the Connector will immediately revert any changes made to the flow so that
> the flow matches what the Connector expects.
> If the desire were to have these flow changes become permanent, a new version
> of the Connector would need to be created and deployed.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
