Describing configurations as a diagram

ewx-cli config describe answers the question a directory of JSON files does not: what relies on what. It renders a configurations directory as a MermaidJS flowchart, one node per configuration grouped by resource type, one arrow per dependency. Trigger schedules also show their schedule.

It describes a directory, not a namespace, so it makes no API calls and needs no permissions. Download first, then describe:

ewx-cli config download demo/enrx_org_001 ./configs --flow test_flow
ewx-cli config describe ./configs

Selecting a subset works as for config download: pass per-resource options or a --resource-file to describe those configurations and their dependencies, or nothing to describe the whole directory. The resource options are repeatable and accept names as well as IDs (--rule my_rule --rule other_rule); given without a value, an option covers every configuration of that type. --output/-o writes the diagram to a file, handy next to a stored configuration set:

ewx-cli config describe ./configs --output ./configs/DIAGRAM.md

The output is a Markdown code block, which renders as an image on GitLab, in most Markdown viewers, on mermaid.live, and on this site: