Requirements VS PoShLog

Does noone manage Hyper-V clustered VMs properly using declarative approaches? I cannot find a single complete approach to managing it. puppet, salt, terraform, even DSC have limited use cases and focus on single node VM creation. System Ctr is is obsolete trash. I was thinking of building something custom using a project (semi-non maintained) here https://github.com/microsoft/Requirements and building out getters and setters but figured I would see if someone has solved for this. It's a shame terraform provider isn't being actively updated because thats probably the most correct way or if bicep/arm templates could be used against on-prem HyperV. Not sure how people can manage this thing without a sane devops approach.

You might benefit from something like Requirements, though you'd probably want to fork rather than use the module which doesn't support pwsh7.

Found the statement above in a repo. Would like to get some opinions on this.

The Requirements framework itself is quite simple to work with. There is a gotcha about using abstractions and control flow statements. You'll need to call .GetNewClosure() to ensure variable values are captured within the defined scriptblocks. The challenging part is breaking down the necessary desired state into its atomic components. A lot of the tools we use try to be helpful and change a lot of system state with a single command. That's great for some informal command-line work, but when you want a reliable script, building a declarative, idempotent script is going to save you time and effort in the long run.