Puppet is an open-source configuration management and automation tool for managing infrastructure and application deployments. It models system state in declarative manifests, enforces idempotent convergence, and enables centralized orchestration of large server fleets. It integrates with cloud providers and CI/CD pipelines.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Puppet is a declarative configuration management and automation tool for managing infrastructure and application deployments using centralized manifests.
Puppet began in 2005 from Luke Kanies’s work on automating administration of heterogeneous Unix systems; Puppet Labs then developed the declarative model for repeatable infrastructure configuration.
Manifests describe the desired state of packages, services, and files. An agent repeatedly compares that state with the machine and applies only required changes; dependencies and roles organize administration across many hosts.
Declarative manifests define target states.
An agent reconciles drift against the target state.
Modules package reusable configuration logic.
Puppet fits standardized server fleets where changes must be repeatable and auditable. Costs arise from modeling the desired state, operating agents, and maintaining platform-specific modules.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.