> This is no where near the level of readiness needed to be reliably used in a production environment.
This is baseless FUD.
Pyinfra is 8 years old, just 2 years younger than Terraform. It's well maintained, stable, and used by many teams in production. Just because it's not as widely known or adopted as other tools, doesn't mean it should be avoided. In fact, as you can see from testimonials here, users often prefer it over Ansible.
> Should probably just stick with the Terraform CDK or Chef if you need this level of expressibility.
Terraform is used for provisioning infrastructure. Pyinfra is a configuration management tool. They're not equivalent.
Chef is closer, but it's an older tool that has largely been superseded by Ansible. It shouldn't be anyone's first choice, unless they really need some obscure feature it does better than Ansible, or Puppet for that matter.
> Verbose logging is not a reason to introduce a non-standard tool into your stack.
Why would that be the only reason to use this? That's not even one of its prominent features, and surely all tools in this space support verbose logging...
This is no where near the level of readiness needed to be reliably used in a production environment.
Verbose logging is not a reason to introduce a non-standard tool into your stack.