I am trying to understand how to integrate NiFi within an existing SDLC. The following are some challenges that I am trying to resolve:   1) I am aware that NiFi Registry 0.2.0 allows us to add a git flow persistence provider. This means on every commit to the Registry, the flow file will be automatically be saved to the git repo. Is it possible to take the NiFi Registry out of the picture entirely and work solely with git. I have the feeling that there is a good reason to tightly integrate NiFi with NiFi registry, I would be really helpful if some one can explain the rational behind this tight integration.   2) Is it possible to deploy a NiFi flow from an artifactory instead of the NiFi Registry? A reference to an example would be really helpful.   3) Lets say I have a bunch of NiFi custom processors that needs to be hosted on git and there is Jenkins in this SDLC. Jenkins does the auto build of each custom processors and deploys them in the artifactory. Also the flow file, which would use these custom processors needs to be promoted to higher environments (dev, qa, prod) along with the Custom Processors (nar files). How should one design the SDLC for NiFi Custom processors and the flow file. Should all the custom processors and the flow files be in the same git repo? can each of the custom processors be part of the same project but be placed in their own package such that separate nar files are created while the flow file is also part of this project? Not sure I am making any sense any more at this point, please let me know if that is the case. ... View more