Puppet Best Practices: Design Patterns for Maintainable Code
Puppet Best Practices: Design Patterns for Maintainable Code
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 Main...
3. Coding Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Swiss Bay
These wrap component modules to define a specific technology stack (e.g., profile::webserver ). They handle local logic and Hiera lookups. 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
A good module follows the : it should do one thing and do it well. Puppet Best Practices - The Swiss Bay Coding Practices
These are the building blocks (e.g., puppetlabs-apache ). They handle the "how" but shouldn't contain business-specific data.