Me and my team has below set of question related to Apache Nifi.
The best practice to organize team development of the nifi workflow that includes:
-Flow source control (merge, diff, …) - should it be done for template or for the full flow ?
-Sharing templates question : through the source control or through the shared nifi instance ?
-Controller Services are duplicating during template export – is it a bug or the feature that we don’t understand how to use?
How to deploy the configured flow on the nifi cluster? Through the template import or full flow substitution with nifi restart?
@sachin tiwari This below post does not answer all of your questions but it answers some and addresses the spirit of the perspective you are seeing this from (team dev / SDLC):
Based on the details shared on above link, I was thinking of doing below steps.
The main idea behind creating multiple template is to have a capability to deploy specific template (process group) as compared to entire flow in any environment. Will it be a good idea as I can see that with this approach, no of templates tends to increase and merging will be difficult.
I think it all depends on what the unit of deployment is.
It is pretty much like a software code base: what needs to be deployed together? That unit of deployment is branched by separated teams, changed and merged among all teams for deployment, using standard change-management models.
I am still not clear on how can I get my multiple developer work on same Nifi flow. Shall I be running a single centrally hosted Nifi, and ask my team to work on it so that my flow.xml will always have latest changes and commit this flow.xml on a daily basis. But with this I will not have flexibility of deploying individual component. Any thoughts on this?