... associated bits like config nodes (and credentials), plus sub-flows, plus packages, etc.
First I thought I should learn how to use the API and build some routines to go through a given flow and identify config nodes, sub-flows, packages and start with a list/report of what won't be copied.
I've looked at the flow json structure, the awkward settings.js file, the package.json file, and the .config file. It seems that by cross referencing these files I could come up with what's missing.
- Can someone suggest a way to start? What exists? What am I missing?
- Why doesn't the export flow cover things like missing npm installs?
- How about including things defined in functionGlobalContext?
- Can the API be accessed, for example the Admin API Method GET /settings, from within a function node in a flow? If so, is there an example?
- Is this a fool's errand?
I think at some point I'd like to find a way of updating a flow and it's parts via ansible and/or some kind of continuous deployment method.
Thanks for any tips.