Thanks for the rapid response. Really appreciate it.
Let me explain what I am trying to accomplish. I've built a system whereby instruments are auto-configured as they attach. Each new instrument requires an instance of a single flow, using different ports, so I have an env variable for the flow's port.
When I inspected the json when prototyping, it was clear how to add a reference to an existing flow with env variables set to that specific instance. So I GET flows, add the reference and POST to flows the entire json:
I sed my instance values in for MQTT_PORT, XXX, YYY and so long as I seed the initial flows with my original json, all is fine. As a part of the automated setup process to add a new instrument, the only thing preventing this to be 100% automated is the requirement to click MERGE in the UI.
IF just calling /flow with a new reference doesn't bring up a MERGE, I could try to refactor with that approach. Not sure how to transform the above to a /flow payload that will add without a MERGE request. If you think this is the right path, please let me know.
Guidance appreciated and thanks again.