Keep your logic in your profiles and your specific values in your Hiera YAML files. 3. Maintainable Module Design
Puppet Best Practices: Design Patterns for Maintainable Code
Writing Puppet code is easy; maintaining it as your infrastructure grows from five nodes to five thousand is the real challenge. To avoid "spaghetti manifests" and technical debt, you need to move beyond simple scripting and embrace declarative design patterns. 1. The Roles and Profiles Pattern Puppet Best Practices: Design Patterns for Main...
These wrap component modules to define a specific technology stack (e.g., profile::webserver ). They handle local logic and Hiera lookups.
A good module follows the : it should do one thing and do it well. Puppet Best Practices - The Swiss Bay Keep your logic in your profiles and your
This is the "gold standard" for Puppet abstraction. It separates your technology-specific code from your business logic, making your codebase modular and readable.
These are the building blocks (e.g., puppetlabs-apache ). They handle the "how" but shouldn't contain business-specific data. To avoid "spaghetti manifests" and technical debt, you
Puppet Best Practices: Design Patterns for Maintainable Code