Pyinfra: Automate Infrastructure Using Python

What Pyinfra Is and How It Compares

• Described as an agentless configuration management and orchestration tool, broadly “like Ansible.”
• Uses Python as the definition language instead of YAML/Jinja. Operations are Python functions (often decorated) representing either stateful “ensure X is true” or stateless “run this command.”
• Can handle both ongoing configuration management and ad‑hoc commands across many hosts.
• Integrates with Terraform primarily as an inventory source: Terraform provisions resources; Pyinfra configures them.

Perceived Advantages Over Ansible and Others

• Many commenters dislike Ansible’s YAML + Jinja templating, especially loops, conditionals, and data reshaping. They find pure Python easier to reason about, test, and reuse.
• Pyinfra execution is reported as significantly faster than Ansible; performance was a motivating factor.
• Debugging is said to be simpler: real-time stdout/stderr, “just commands over SSH,” fewer layers of magic.
• Inventories and variables as Python code (not static files) are seen as powerful for dynamic environments.
• Some users successfully replaced a mix of shell, Chef, and manual changes with Pyinfra, especially on platforms where Ansible’s module coverage is weak (e.g., macOS, Fedora CoreOS without Python).

Limitations, Gaps, and Open Questions

• Documentation and landing page are widely criticized for not clearly answering “what problem does this solve vs Ansible/Terraform/Salt?”
• Out‑of‑the‑box cloud provisioning (e.g., AWS autoscaling groups, RDS workflows) is limited; expectation is to pair with Terraform or write custom logic.
• Not all operations are strictly declarative/idempotent; some are explicitly “stateless shell.”
• No built‑in agent model; it’s SSH/local based, though a looping “agent‑like” mode is considered trivial.

Broader Debates: Tools, Paradigms, and Languages

• Ongoing debate over declarative vs imperative approaches, and whether Ansible or Pyinfra are truly declarative.
• Some argue configuration management is increasingly superseded by immutable images, containers, and cloud‑init; others insist something still must configure base systems.
• Python as infra language draws mixed reactions: praised for familiarity and power vs criticized for packaging, typing, and long‑term confidence.
• Alternatives mentioned: Ansible, Puppet, Chef, Salt, Fabric, Pulumi, Terraform/CDK, NixOS, Packer, cloud‑init, and various homegrown tools.