I want to be able to promote code throughout our environments without having to manually update any of the processors in the UI after deployment. So far, I've seen people talk about copying the flow.xml.gz file over and restarting the service, but I don't see this working in a real world scenario because you would have to promote the entire environment and not just the code changes that were ready to be deployed. Another option, which I think is more likely, is to create a temple, export it, and import it into the next environment. This works well, and I can use the custom properties file with the expression language to handle most of the configuration changes, but when I import a template that references a controller service, it always creates a new controller service instead of using the existing one. This happens even when I copy and past a process group within the same environment or create a new process group from a template within the same environment. I end up having to delete that controller service that is created automatically and update the processor to use the existing controller service. What I would like to do is export the template from UAT, for example, and have a script that would use a mapping of controller service ids from UAT to the matching controller service in PROD and update that value in the XML, so when I import the template it finds the existing controller service instead of creating a new one, but when I update the controller service id and then import it, it updates the id again automatically and then creates a new controller service instead of using the existing. Has anyone dealt with this type of issue before and have any ideas of workarounds?
... View more
