You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Bryan Rosander (JIRA)" <ji...@apache.org> on 2019/04/29 19:23:00 UTC

[jira] [Created] (NIFIREG-260) Ability to rebase registry changes and push them upstream

Bryan Rosander created NIFIREG-260:
--------------------------------------

             Summary: Ability to rebase registry changes and push them upstream
                 Key: NIFIREG-260
                 URL: https://issues.apache.org/jira/browse/NIFIREG-260
             Project: NiFi Registry
          Issue Type: New Feature
            Reporter: Bryan Rosander


 

A branching workflow with the NiFi registry would empower developers to make their own changes in a branched version of the registry and only promote changes upstream after local testing/peer review.

Due to the linear versions and lack of branching, it currently isn't supported for multiple developers to make independent changes to a registry and merge the results in.

With the introduction of aliasing functionality [1], it is now possible to "branch" the entire registry and spin up a NiFi instance pointed at the branch.  What is still missing is the ability to take changes made to the branch and apply them back upstream (even if there have been changes to the upstream in the meantime)

A nifi-registry-toolkit "rebase" functionality would make a branching workflow possible.

 

[1] https://jira.apache.org/jira/browse/NIFIREG-238



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)