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)
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...
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 These are the high-level descriptions of a machine's
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. Separation of Code and Data (Hiera) Keep your
Puppet Best Practices: Design Patterns for Maintainable Code
Use Hiera to provide defaults and overrides based on facts like environment or OS.
This is the "gold standard" for Puppet abstraction. It separates your technology-specific code from your business logic, making your codebase modular and readable.