IMHO, the issue is that Ansible uses YAML to do "programming language" sorts of things, which is why it feels so unnatural. I tried an experiment last year: Wh

IMHO, the issue is that Ansible uses YAML to do "programming language" sorts of things, which is why it feels so unnatural. I tried an experiment last year: What if Ansible had Python rather than YAML syntax. https://github.com/linsomniac/uplaybook?tab=readme-ov-file#simple-examples https://github.com/linsomniac/uplaybook?tab=readme-ov-file#s... The downside is that having full Python available makes it really easy to make your playbooks non-idempotent, which Ansible gate-keeps behind Ansible modules. Also someone raised a concern that full Python (rather than a more limited safe dialect like Starlark) would make it harder to trust third-party playbooks. But considering uPlaybook's use case (ansible-like system configuration) it feels like even with a restricted dialect it is going to have plenty of opportunity for nefarious purposes. I've put out uPlaybook for some limited review among my friends, and I've gotten some excitement about it. It doesn't have fleet management and remote running though, which is the big negative feedback I've gotten. I'm interested in thoughts on it though.