Thats right they are identical, and registry-dev.properties has 2 more fields, one that is baseUrl https:// registry:port, and the other proxiedEntity is left blank..
/baseUrl=https://nifi-registry.xx.local:18443 proxiedEntity=/ So using those NiFi properties the CLI can only talk to the Registry, is that right? Meaning these commands we expect to succeed /> registry list-buckets -p registry-dev.properties/ but any command that calls to 'nifi' from the CLI, we expect to fail? /> nifi pg-start -pgid .../ >From inside NiFi container I am able to ping that Registry address, and the port is indeed listening in Registry.. The url I used for Registry is the same URL that I specified in NiFi UI for Registry and I was able to get buckets && version flow (of my processor group). -- Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
