We are trying to implement best practices in regards export/import via NiFi Registry. Currently we have one DEV site and multiple operational sites, ideally we would export from DEV and import into our various OPS sites. With that in mind I have a few questions:   What is the best way to provide site-specific configuration for the controllers/Processors? Should we have a unique properties file for each site and we select which one to deploy per site? According to some documentation, later versions of NiFi are planning to remove support for this kind of unique property file loading. Is there a way in the controllers/Processors to provide conditional values based on deployed site? Of particular concern is our Solr "Zookeeper Host List" This is a property value on our Query and Ingest processors, and they currently aren't enabled to support the Variable Registry, so the value is explicitly provided (no variable lookup/replacement). Do we need to set up and use a "Variable Registry" at each site? Is there a way to import a set of variables or do we have to define the variables via the UI? Documentation again suggests moving away from variables, and use parameters instead. Should we use Parameters instead. What is the best way to manage/deploy site-specific set of Parameters? What is the best way to export from one NiFi Registry, import into another NiFi Registry instance, and then trigger the associated NiFi instance to update its workflow reference? Does the update need to be triggered via the UI, or can the update be automated? ... View more