Huh, are the projects clawed back from #puppet , namely #choria and #OpenVox #OpenVoxProject, the only entries in #ConfigurationManagement without LLMs in them?
Huh, are the projects clawed back from #puppet , namely #choria and #OpenVox #OpenVoxProject, the only entries in #ConfigurationManagement without LLMs in them?
@pertho https://github.com/ansible/ansible/tree/devel/.claude/skills
https://github.com/ansible/ansible/blob/devel/AGENTS.md
Uh, what? https://github.com/ansible/ansible/commit/883360fa0068bfc65b35906909fa1f6388153a17
https://github.com/ansible/ansible/commit/52b7d4d092359e776da0b79db9752bfc6ca91969 though it took me some time to reach a commit that would mention an LLM
@viq Are there any tools like Ansible that aren't slopified? Saltstack?
Maybe I should just write a shell script instead. 😂
Sigh, is it time to move my shit to #CFEngine? I guess I will need to look a bit what's been going on with that.
If the slop doesn't matter, the big players in the space: Ansible, Puppet, Chef, Salt, and CFEngine.
Or a big pile of shell-scripts. 😆
However, I don't know which of them have been slopified or to what degree if that matters.
@gumnos Yeah, I'm aware of all the big players and have used most of them. One day I'll work out a better system, but I tolerate them for now 😂
My biggest complaints fall along the lines of:
1) blurred lines between idempotent-ish ops and non-idempotent ones
2) creating (or even tacitly encouraging) a divide between "prod" and dev environments.
One might conclude from this post that I should just use Nix for everything 😂 And I might eventually land there. But Nix has a STEEP learning curve.