Hi all, I'm faced with the challenge of deploying copies of identical flows for several "environments" on the same canvas. With the help of parameter contexts, this mostly works. Where it breaks down is the remote process groups and the remote input ports specified on the connection going to the RPG. There is no way to parameterize this it seems, so I started looking at "fixing" the destination port in the json file outside of nifi/registry. I've been able to replace the destination port, but only if the new port already exists in the list of remote input ports found in the json file. If the flow is deployed to a newly filled canvas or different server, it breaks down, the same if the port was recreated after the flow was committed.
Is there any in-depth documentation other than the source code itself on how NiFi and the registry treat the various id, instanceid and name fields for flow being imported? It seems that remote process groups work differently from processors and connections and I've been unable to determine the "rules" through trial and error so far. Any pointers would be greatly appreciated! Regards, Isha
