The so-called highstate data structure is very stable and well documented so Renders rarely need changes:
https://docs.saltstack.com/en/latest/ref/states/highstate.ht...
The regular Python interface you mentioned is my favorite too, when YAML/Jinja aren't a good fit, and people do use it. It's 40 LOC and has only needed 32 commits in the six years it's been around:
https://github.com/saltstack/salt/blob/5406a7cdd4729/salt/re...
The takeaway is YAML/Jinja generate exactly the same result as the Python Renderer so use what you like.
I had the feeling that YAML is the one that addresses your criticism ("I like YAML as configuration file language, but it's terrible for DSLs."). And yes, I do use the python one and I am very happy with it.
> The YAML is the default, and it's what you find examples and support for (Stack Overflow and so on)
Pro tip: if they are YAML on StackOverflow, you don't have to copy-paste them, but more rather translate them to the representation that satisfy your high requirements.
The YAML is the default, and it's what you find examples and support for (Stack Overflow and so on). I get the impression that many of the renderers are not "official", in the sense that they're maintained by other people.
If Salt only provided a Python API, the situation would be different. As such, it's a case of too much choice, and not enough standardization. There are no less than three competing Python renderers.