Puppet Best Practices: Design Patterns For | Main...

These are the building blocks (e.g., puppetlabs-apache ). They handle the "how" but shouldn't contain business-specific data.

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 are the high-level descriptions of a machine's function (e.g., role::app_server ). A node should ideally have only one role . 2. Separation of Code and Data (Hiera) These are the building blocks (e

Puppet Best Practices: Design Patterns for Maintainable Code To avoid "spaghetti manifests" and technical debt, you

Puppet Best Practices: Design Patterns for Maintainable Code

3. Coding Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Swiss Bay