An approach to reusable stack modules
What we have seen until now are more or less standard and mainstream Puppet documentation and usage patterns, and I have surely forgotten valuable alternatives. I may have left traces of personal opinions on some solutions, but they are all common and existing ones; nothing has been invented.
In this section, I'm going to discuss something that is not mainstream, has not been validated in the field, and is definitively a personal idea on a possible approach to higher abstraction modules.
It's not completely new or revolutionary: I'd rather call it evolutionary in the line of established patterns such as parameterized classes, the growing usage of PuppetDB, and roles and profiles, with a particular focus on reusability. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access