Everything is in a Puppet catalog

2026-06-21
model: gpt-image-2
Near-white technical zine aesthetic with black ink, one strong red accent (#cc0000), sparse 2005 web sensibility, philosophical but legible. Create a polished wide infographic visual for "Everything is in a Puppet catalog" about Life as a Puppet catalog. Context: Treat the reader as a peer with sysadmin depth but possibly new to Puppet's model. Give a complete picture of what a Puppet catalog is and how it comes to exist: the resource type system, the provider abstraction, manifest and module structure, the full compilation pipeline (node classification, fact injection, code evaluation, graph output), Facter and the fact trust boundary, relationship metaparameters and containment, dependency ordering and refresh signals, Hiera and data separation, the role/profile/module pattern, exported resources and PuppetDB, the agent run loop, idempotent convergence, drift, noop mode, and reporting. Narrate as the catalog itself — a compiled, agent-specific resource graph that embodies declared intent. Emphasise the declarative model and its consequences: ordering is explicit, convergence is automatic, and the catalog is not a script but a specification of desired state.. Key points to visualize: Resources and the type system; Manifests, classes, and modules; Catalog compilation; Facts and Facter; Ordering, relationships, and dependency edges; Hiera and data lookup; Exported resources and PuppetDB; The agent run cycle and idempotence. Use concise labels only; avoid paragraphs and tiny text. Leave the detailed explanatory copy to the surrounding HTML page.
Life as a Puppet catalog