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.

A good module follows the : it should do one thing and do it well. Puppet Best Practices - The Swiss Bay 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

These wrap component modules to define a specific technology stack (e.g., profile::webserver ). They handle local logic and Hiera lookups. Puppet Best Practices - The Swiss Bay These

Never hardcode configuration values like IP addresses or package versions directly into your manifests. Use Hiera to keep your code "clean" and your data flexible.

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