PyInfra 3.8.0

Original Article ↗ Hacker News Discussion ↗

Overview of PyInfra 3.8.0

  • Agentless infrastructure automation tool similar in role to Ansible/Salt/Chef: SSH into hosts, gather facts, compute diffs, converge to desired state.
  • Core differentiator: “playbooks” are plain Python modules, not YAML/templating/DSL stacks.
  • Operations are idempotent; execution model is “diff then apply”, similar in spirit to Terraform.

Python vs YAML / Configuration-Language Debate

  • Many comments praise moving away from YAML + Jinja + custom DSLs, citing:
    • High cognitive load.
    • Awkward conditionals, loops, and data manipulation.
    • Fragile typing and indentation issues.
  • Counterpoint: restricted DSLs and non–Turing-complete languages provide analyzability and safety; full Python can be over‑expressive and easier to misuse.
  • Some advocate intermediate approaches (e.g., Starlark-style restricted Python) to balance power and guarantees.

Comparisons with Ansible, Salt, Chef, etc.

  • Several users report migrating homelabs or small/medium estates from Ansible to PyInfra:
    • Find PyInfra easier to reason about and debug.
    • Appreciate standard Python structure (modules, functions, classes) and editor support.
  • Ansible criticisms:
    • Slow execution.
    • Complex data manipulation.
    • Sprawling role structure and YAML/Jinja interplay.
  • Salt/Chef/Puppet noted as heavier (agents, servers) versus PyInfra’s SSH-only model.
  • Some argue Ansible’s declarative YAML and “paved path” reduce footguns; see PyInfra as potentially more brittle due to arbitrary Python.

Performance & Developer Experience

  • Multiple reports that PyInfra feels dramatically faster than Ansible; one suggests 10x is conservative.
  • Users like:
    • Clear function signatures with type hints.
    • Easy creation of custom operations and facts in Python.
    • Direct integration with other Python tools (e.g., boto, pytest, Consul).

Limitations, Issues, and Design Quirks

  • Conditional execution model is not purely “just Python”; _if operation parameter and two‑step diff/apply are acknowledged compromises.
  • A long‑standing Paramiko SSH bug (host key handling) is a blocker for some; maintainers are considering moving away from Paramiko.
  • Ecosystem still smaller than Ansible’s; some gaps (e.g., hardening playbooks, orchestration dashboards like Ansible Tower) are noted or only aspirational.

Tooling, AI, and Ecosystem Integration

  • Some users pair PyInfra with Pulumi for end‑to‑end “infra in Python” (cloud resources + servers).
  • LLM use is discussed:
    • YAML’s rigidity can help models, but others prefer feeding models curated PyInfra examples and docs.
    • There’s ongoing work on llms.txt metadata to steer LLMs toward current (v3) APIs.