Everyone seems to agree how super duper cool is Infrastructure as Code, but you all are just doing Infrastructure as JSON or Yaml which gets transformed into complex behaviour by someone in the middle that nobody actually fully understands in neither of the sides.

Maybe, probably, using actual code to do it, is plausible, I dunno.

And maybe using a full fledged programming language with its editor, linter, compiler, etc, might be worth.

And if not, why aren't you all using NixOS or something like that, handling natively in your system the logic to transform definitions into infrastructure, instead of using a tool that needs to store an state separately so it doesn't blow up in thousand pieces because *guess what* idempotency is pretty hard in an imperative system driven by command line software.

Yes I'm talking about Terraform, Pulumi and similar stuff.

"Where to put the state" is the most common hidden vendor lock behind a lot of IaC-SaaS out there.