Joe, The workflow I am interested in is the dev/int/prod workflow with multiple devs and continuous integration.
Cheers, Edgardo On Tuesday, April 28, 2015, Joe Witt <[email protected]> wrote: > Esteban, > > Thank you for providing so much detail to what you're trying to do. I > want to walk through this further with you to better understand the > perspective. But first I will say that the pain you refer to with > removing a flow is something we will sort out. You should be able to > simply right-click and delete so we will improve that until it is > true. > > Can you explain why you want to build on one instance, then make a > template, then go to another instance? I am wondering if this is a > sort of dev/integration/production workflow. > > I think our general philosophy has been to enable developers to easily > build new extensions which are effectively unit tested and then put > those out on the instance where the data is flowing. We then optimize > extensively around the operations/administrator experience. We've > seen a consistent theme of need though to clarify how the developer > experience can/should work. So happy to take more feedback on what > you're trying to do and also 'why' you're trying to do it so we can > help guide and so we can learn how to adjust as needed. > > Thanks > Joe > > On Tue, Apr 28, 2015 at 8:49 AM, Esteban Aliverti > <[email protected] <javascript:;>> 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
