Sachin I think the most common approach is that developers focus on building reusable components and integration testing in local or integration test environments. Those components, fully documented, are made available to operations teams who weave those components and their recommended configurations into the live feeds. At times the developer and the operations person are actually the same person but they're wearing different hats when doing these things. In such a model the developer can also help by offering well scoped templates that reflect how to wire together that component with other necessary components to achieve a greater function. Those templates can certainly be version controlled. Presently that is done outside of NiFi but we do have a concept of a template registry with an oustanding feature proposal [1] which will make this even nicer to operate with.
[1] https://cwiki.apache.org/confluence/display/NIFI/Extension+Repositories+%28aka+Extension+Registry%29+for+Dynamically-loaded+Extensions Thanks Joe On Fri, Nov 4, 2016 at 1:38 PM, Sachidanand Tiwari <[email protected]> wrote: > Team, > > I am reaching out to you to seek your recommendation on development > guidelines when multiple teams are working on a Nifi flow. How to manage > source code version?. Do we need to having each functionality as separate > Process Group exported/imported as template?. How to deploy flow on Nifi > cluster environment. > > As per our current approach, we are creating separate ProcesGroup for > different functionality and exporting/importing as template. > > -Sachin
