You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Dennis Seiffert (JIRA)" <ji...@apache.org> on 2019/03/26 12:53:00 UTC
[jira] [Created] (NIFIREG-242) Two-way synchronization of git
repository backed flows
Dennis Seiffert created NIFIREG-242:
---------------------------------------
Summary: Two-way synchronization of git repository backed flows
Key: NIFIREG-242
URL: https://issues.apache.org/jira/browse/NIFIREG-242
Project: NiFi Registry
Issue Type: New Feature
Affects Versions: 0.4.0
Reporter: Dennis Seiffert
With this feature the NiFi user and developer's life using git as version control as a backend for the registry would be easier (especially in dockerized environments). As a conclusion the git repository would be the single source of truth in order to maintain NiFi flows. This feature contains the following abilities without affecting existing functionality:
* synchronize remote git repository with local (nifi- registry) git repository in order to support multiple registries (imagine changing a flow in a test environment and update the flow in a productive environment via feature branches in git, etc. ) and third party systems (git changes not done by the registry, repair broken flow file because of changed registry url in flow xml)
* initial import of git repository into registry's metadata database on startup (see open issue #NIFIREG-227)
* ability to reset local git repository (including metadata database) to the state of the remote repository
* get recent status of synchronization process
* control synchronization via REST- endpoints (reset repository to initial state, pull latest changes from git remote repository
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)