[
https://issues.apache.org/jira/browse/NIFI-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951433#comment-17951433
]
Bryan Bende commented on NIFI-8160:
-----------------------------------
Using latest code on main I see consistent behavior where enabling/disabling a
processor always shows as a local change to be committed to the registry.
Regarding whether it should be tracked or not I think is a hard decision to
make and we'd probably need further input from users. A primary use case for
disabling processors is to avoid spending time/resources on regularly
validating components that aren't even going to run. If you aren't too worried
about the overhead of validation, you can take different approaches where you
configure each cluster with a system property like "env" and have parts of your
flow use RouteOnAttribute based on ${env} to determine if it should route to
this section of the flow based on whether it is dev, test, prod, etc., so
essentially in prod there might be a path in the flow where it doesn't route to
because that path was for dev only.
> Enable / Disable should not be seen as a change in Nifi registry
> ----------------------------------------------------------------
>
> Key: NIFI-8160
> URL: https://issues.apache.org/jira/browse/NIFI-8160
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: DEOM Damien
> Priority: Critical
>
> Enable / Disable should not be seen as a change in Nifi registry.
> It interferes with the release management when we use several clusters (
> integration / production )
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
