[
https://issues.apache.org/jira/browse/NIFI-9512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-9512:
-------------------------------
Affects Version/s: (was: 1.15.1)
Status: Patch Available (was: Open)
> Add git pull to Nifi Registry
> -----------------------------
>
> Key: NIFI-9512
> URL: https://issues.apache.org/jira/browse/NIFI-9512
> Project: Apache NiFi
> Issue Type: New Feature
> Components: NiFi Registry
> Reporter: Oliver Ford
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Nifi Registry allows flows to be pushed to git, but it doesn't allow flows to
> be edited within git, and then pulled back into the Registry. Adding this
> will allow users to edit the flow via branching and merging, and then pull
> into the Registry.
> I have a solution where a new endpoint, */nifi-registry-api/flows/updateGit*
> is added.
> When called, this checks git for updates. If updates are available, they are
> pulled to the Registry's local repository and the flow synchronization is
> called.
> This allows a Nifi instance to then re-add a later version of the process
> group. I will raise a PR for this unless anyone can suggest an improved
> design?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
