[
https://issues.apache.org/jira/browse/NIFI-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529712#comment-17529712
]
Nesa Simon David commented on NIFI-8874:
----------------------------------------
Actually, the groupId and Id identifiers don't change, the problem is caused by
nifi-registry not maintaining the previous ordering of the elements in the
JSON. This problem can be solved by sorting the elements by ID before exporting
the configuration.
> Retain groupId and Id identifiers when importing Flows from registry
> --------------------------------------------------------------------
>
> Key: NIFI-8874
> URL: https://issues.apache.org/jira/browse/NIFI-8874
> Project: Apache NiFi
> Issue Type: Improvement
> Components: NiFi Registry
> Reporter: eric twilegar
> Priority: Major
>
> We started using Nifi registry with Git integration to have some insight into
> the changes being made and create a relatively standard SDLC for our Nifi
> process groups ( read jobs ).
> When we started only one user was making changes and so the git history was
> pretty good.
> When a second user imported a flow to their local machine, made changes,
> committed those changes and we deployed them we took a look in Git to see the
> changes the user had made.
> The git diff was riddled with id and groupId process identifier changes which
> made the history less useful than it could have been.
> I'm not sure what your future plans are for Git so this might come out in the
> wash, but we are looking forward to being able to see the diffs, approve them
> and so on. I realize PRs could be a real issue as this stuff doesn't merge
> well, but eventually we might want a PR from a registry to registry so this
> could all tie together.
> Thanks so much for the great work. Have a wonderful day.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
