Configurations need someway to be explorable

[hwine]

Configurations are hard to interpret for a human for several reasons:

• There can be many <=> many relationships.
• Many of the values are sensitive (and encrypted).
• Different audiences use different namespaces when referring to keys, which often leads to ambiguity in requests and resultant rework.

Sanity of maintainers would be greatly improved if a sanitized (no sensitive material) version of the file could be shared, while still maintaining relationships.

[hwine]

As a first approximation, I think it is safe to make the following assumptions:

• Sensitive values are sufficiently protected if replaced by a sha256 hash.
• Only certain sections of the yaml files are "business logic" that need this treatment.
  • These sections are more structured in terms of what is, or is not, sensitive.

The business logic sections can be converted into a CSV file format, which would be safe to be shared - at least as a confidential document. The CSV file could be further processed into diagrams, or even loaded into sqlite as a datasette.