Use Hiera to provide defaults and overrides based on facts like environment or OS.
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 wrap component modules to define a specific technology stack (e.g., profile::webserver ). They handle local logic and Hiera lookups. Use Hiera to provide defaults and overrides based
Puppet Best Practices: Design Patterns for Maintainable Code Maintainable Module Design These wrap component modules to
3. Coding Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Swiss Bay
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)