Panos What version of NiFi are you using? The issue with the NiFi templates diffs has actually been addressed (see https://issues.apache.org/jira/browse/NIFI-826). So as of NiFi 1.0 you can export templates in a deterministic way and then execute diff on them to see only what was changed. It was addressed specifically for the SDLC issue you are describing. Also, when processor is associated with controller service and you created a template that includes such processor, its dependent controller service will end up on the template and back in your environment once such template is imported.
Anyway, give it a shot and let us know. Cheers Oleg On Jan 13, 2017, at 4:49 AM, Panos Geo <[email protected]<mailto:[email protected]>> wrote: Hello all, We have a Continuous Integration/Continuous Development pipeline that involves for each stage (development, testing, customer deployment) a dedicated virtual machine running a NiFi instance. As such, for each stage of the pipeline we have to migrate the changes of our NiFi canvas from one virtual machine to another. For this we encounter two big problems : 1. As far as I know, there is no easy way to diff NiFi canvases (or templates) so that we can recognize the changes and don’t have to export and import the full canvas each time (as there are configuration changes in the target VM that we wouldn’t like to overwrite). 2. If we have to export the full canvas, is there a way to reassociate processors with the required services on the target virtual machine (e.g. DBCPConnectionPool or HTTPContextMap) without having to go through each processor explicitly and do the reassignment? Many thanks in advance, Panos
