Hi all, It appears the NiFi Registry is the established solution for flow versioning/deployment/upgrades, however it seems to have a centralised architecture such that any server with NiFi running on it must be able to connect back to a centralised server running the Registry in order upgrade flows. My scenario is I have an isolated server that can't make external network connections, but I can transfer files to it. This means I can e.g. transfer NiFi templates to deploy into the NiFi instance, but I can't connect that NiFi back to a Registry to upgrade the flow to the next version. How do I programmatically upgrade the flow? I had a brief look at exporting some data out of my Registry into the server's Registry instance - that way I could do an upgrade by communicating to the local Registry. However I found that the h2 database was needed as part of the export, and trying to integrate multiple developers' h2 databases into one h2 database to be used by Registry seemed difficult to do in a reliable way. Are there any alternatives to either the Registry or this centralised approach for upgrading flows from e.g. version 1 to version 2???
... View more
The above was originally posted in the Community Help Track. On Tue Jun 4 01:52 UTC 2019, a member of the HCC moderation staff moved it to the Data Ingestion & Streaming track. The Community Help Track is intended for questions about using the HCC site itself.
... View more