This is awesome! We have been iterating on something similar under the digger.dev "umbrella" (terragen.dev (no longer works), awsbootstrap.io, terrabook.io) and

This is awesome! We have been iterating on something similar under the digger.dev "umbrella" (terragen.dev (no longer works), awsbootstrap.io, terrabook.io) and most recently - dgctl: https://diggerhq.gitbook.io/trowel-docs/getting-started/what-and-why https://diggerhq.gitbook.io/trowel-docs/getting-started/what... We strongly believe that some kind of a layer above present-day IaC is missing and badly needed. What exactly is the right solution isn't 100% clear just yet; but it is along the lines of a generator / framework / compiler / "OS" that would provide reasonable defaults without taking away flexibility. Then there's also a challenge of one-off usage; generator alone is only useful once; a framework on the other hand is helpful all the way throughout the project's lifecycle. Terraform looks like the best (only?) "underlying" IaC, more like a target "assembly language" using the LLVM parallel. The crux seems to be the runtime - it is less about any given state of infrastructure (that's already captured pretty well with existing IaC tools) and way more about the logic of transitions between those states. Managing state / running it on the server (the "CI for infrastructure" use case eg TF Cloud / Spacelift / Env0 etc) seems to be the logical extension of the baseline case of initial provisioning. We started with this, but now are viewing it as secondary consideration that will fall into place once the baseline framework scenario is figured.