I think that just touches on the biggest issue I am struggling with, which is how does nifi fit into my normal developer workflow. That is git, Jenkins, etc. I have also done what you have described but that isn't very developer friendly.
What is the prescribed development methodology is recommended for using nifi in a group development environment? On Tuesday, April 28, 2015, Esteban Aliverti <[email protected]> wrote: > Hi guys, > I was wondering what is the best way to replace a complete workflow in > NiFi. > My scenario is that I have multiple instances of NiFi running the same > workflow. At some point, when changes are introduced into one of the > instances (let's say a new processor is introduced) I would like to > replicate the changes to the other instances. For small changes, things can > be easily handled, but for big changes - introduction of a whole new > branch, for example - things are not so easy. > Given that the workflows I'm currently using are in dev stage, I don't mind > to lose any FlowFile that already exists in the NiFi instance I'm updating. > > The way I'm currently handling this is: > 1.- I create a new template from the NiFi instance where the changes were > introduced. > 2.- I export the template as an xml file. > 3.- I import the template in the NiFi instance where I want the changes to > be applied. > 4.- I manually remove any processor from the NiFi instance where I want the > changes to be applied. (for complex workflows, this step is a real pita!). > 5.- I use the template I've previously imported in the NiFi instance where > I want the changes to be applied. > > My question is: what is the best way to achieve this? > Is there any way to completely delete the workflow that NiFi is currently > executing? > > Regards, > > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX > > Esteban Aliverti > - Blog @ http://ilesteban.wordpress.com > -- Cheers, Edgardo Sent from Gmail Mobile
