I have a set of nodes based on same core in same project
Now I want to split them to different projects for deploy
And I want still keep single project as source of such nodes
I was success to make a monster jsonata expression which takes nodes I want to keep and cut out all other and their childs using recursion, id, g , subflow:id and z attributes
But, there left config nodes and I can't get how to detect them in flows.json
So the questions -
May be there any easer way to programmatic export nodes from flows.json (like export ui does) ?
If not, how to detect config nodes for remove if no left node uses it ?
I looking for solution from runtime, because I injecting it into CI pipeline, so when I building docker image I run node in automated mode, which generates splitted jsons.
Also node.js with running parts of node red would be better than I did.
yeah, very disappointing solution, any plans to change this anyway ? It makes some inconviniences in my case not fatal , but it would be really good to have it possible to make exports serverside in some common way.
Yes, I think it is flaw in flows arch, would be nice to have at least some common attribute shared between control nodes (even "control_node": true would help)