Hi, I want to send specific flowfiles to a specific remote MiNiFi Java. Testing with 1 MiNiFi works great, out from NiFi, into MiNiFi for processing. I'm prepping the MiNiFi flow on NiFi, templating, exporting, converting to yaml, modifying any security settings i need and restarting MiNiFi to accept the updated config.yml. Now i'm adding additional MiNiFis. On NiFi I've setup a PG with a RouteOnAttribute (Attribute is the specific MiNiFi name) to send to a specific S2S Output Port for that MiNiFi. Up to here, all seems fine. The problem i have is in the MiNiFi template. I have the RPG going into a processor, and that's when i specify the From Output Port which is specific to the MiNiFi. How can i template/generalize/variabilize/other the From Output so that i don't need to make separate template for each and every MiNiFi instance? I could theoretically move the RouteOnAttribute from the NiFi to the MiNiFi side but at that point it means i already sent a ton of data to all the MiNiFi instances instead of only to the one that's supposed to get it. I figured i can update the config.yml with the specific connections IDs, but that seems like a broken process that's very prone to mistakes and maintenance for every change i make to the flow. Does anyone have any pointers or tips for this situation?
... View more
An additional note for anyone coming here that isn't seeing the Generated Username/Password log entries (for example on Docker), you can set those by running bin/nifi.sh set-single-user-credentials <Username> <Password>.
... View more