[
https://issues.apache.org/jira/browse/NIFI-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951441#comment-17951441
]
Joe Witt commented on NIFI-8160:
--------------------------------
The lens we used to take for this was thinking about disabled/running state as
a deployment specific concern and so I believe we kept that out of the strict
version compliance calculation. We saved whatever the user had there but would
not force it to impact whether version was still compatible or change it when
updating versions.
However...the game is changing and nifi clusters are becoming more ephemeral
and more flows are CI/CD or programmatically controlled.
I hate to suggest it be optional as we already have too many optional things...
> 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: Major
>
> 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)
