Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-8851

Two-way synchronization of git repository backed flows

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • NiFi Registry

    Description

      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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            DennisSeiffert Dennis Seiffert

            Dates

              Created:
              Updated:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m

                Slack

                  Issue deployment