Yeah there's a lot of churn going on, but the infrastructure space is innovating in really interesting ways right now. On one side you have things like Pulumi diving into the full programming language for configs, on the other side you have an entirely different ethos of git-ops where you only have 'dumb' JSON/YAML configs and store all their state in a git repo with hooks to deploy and manage everything--(ArgoCD, flux, etc. are tools here). And in the middle you have some ideas for non-turing complete languages like Starlark, Jsonnet, Cue, Dhall, etc. to let you do some config generation but limit the risk of building broken configs.

There's really no definitive 'winner' or best option yet. Each has strengths and weaknesses relative to others. It might just come down to how a team prefers to manage and work with infrastructure.