Jo Rhett wrote:
> Well the exact answer to your question is:
>
> lookup("roles::${category}::${class}::classes", Array,
> 'unique').include()
>
> However, the code you've shown is implementing a hierarchy for class
> assignment duplicative of the Hiera hierarchy. Why not use Hiera's
> hierarchy
Well the exact answer to your question is:
lookup("roles::${category}::${class}::classes", Array, 'unique').include()
However, the code you've shown is implementing a hierarchy for class
assignment duplicative of the Hiera hierarchy. Why not use Hiera's
hierarchy to your advantage?
hiera.yaml:
Do yourself a favour, define puppet classes and resources in puppet code. There
are surprisingly few people who can look at puppet resources in yaml and
conceptualize which portion is causing that odd ruby+yaml error.
This is a useful model for how to lay that out:
Hi,
I want to include hiera classes.
---
roles::webserver::apache::classes:
- my_apache
roles::backup::bacula::classes:
- bacula
roles::timeserver::ntpd::classes:
- ntpd
roles::databaseserver::mysql::classes:
- mysqld
I used to use the follwoing (ugly) code in nodes.pp to do so:
if
