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

Puppet Best Practices: Design Patterns for Maintainable Code

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

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...

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)

Use Hiera to provide defaults and overrides based on facts like environment or OS. Puppet Best Practices: Design Patterns for Maintainable Code

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.

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...

Puppet Best Practices: Design Patterns for Maintainable Code