Philipp Freyer created NIFI-15232:
-------------------------------------
Summary: Nifi should allow connecting a ProcessGroup to an
existing flow configuration stored in GitHub (Create from GitHub)
Key: NIFI-15232
URL: https://issues.apache.org/jira/browse/NIFI-15232
Project: Apache NiFi
Issue Type: Improvement
Components: Flow Versioning
Affects Versions: 2.6.0
Reporter: Philipp Freyer
Attachments: image-2025-11-19-12-37-52-912.png
h2. Problem description:
When I start versioning a flow with the GitHubFlowRegistry client, I basically
create a flow definition file in a folder on a GitHub branch.
However, if I accidentally delete the versioned process group and try to
recreate it, I cannot link to the existing file.
!image-2025-11-19-12-37-52-912.png|width=293,height=410!
This can be mitigated, if the process group above the deleted process group is
versioned as well, since we can then roll back the changes. However, if we are
talking about the root process group or about transporting a flow definition
between Nifi instances, this is not possible.
A use case is realizing a development / testing / production environment
separation using Git Branches in GitHub with the ability to transport the
definition between the environments using pull requests. In this case, it is
finicky at best to do the initial configuration, since equal process groups
have to be created and versioned on each instance and conflicts must be
resolved when initially merging changes between branches.
h2. Proposed solution:
The ability to simply connect an empty process group (or a process group during
creation) to an existing versioned flow file on GitHub (defined by the same
flow name in the API, possibly similar to how a process group can be created
from a JSON flow file upload) would be great for the user experience with
GitHub versioning.
It also allows for restoring a NiFi instance configuration from GitHub in case
of server changes or missing backups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
