[
https://issues.apache.org/jira/browse/NIFI-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078437#comment-18078437
]
Jens M Kofoed commented on NIFI-8160:
-------------------------------------
[~joewitt] I can see you have been chatting about this issue.
We are currently using v. 2.9.0 and having some issues about this. We have a
parent PG which is in version control. this flow has a child PG which has its
own version control. If we disable the hole PG NiFi is saying that local
changes has been made. If we enable everything again some time the child PG
still says local changes has been made. But if you list which changes has been
made the list is empty. If you revert, the list is also empty but after revert
the child PG is back to normal
> Enable / Disable a process group 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 a process group should not be seen as a change in Nifi
> registry.
> It interferes with the release management when we use several clusters (
> integration / production )
> When pulling a Flow file from the registry, it should always be enclosed by a
> Process group (which is not always the case) that we could disable without
> beeing seen as a change.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
