Joseph,
So, the problem with this method appears to be that once you specify
"hiera_include('classes')" in the environment's site.pp, Puppet appears to
try and make Hiera the ONLY source for node classification. I rely on
roles from my ENC and profiles for classification as well.
Josh
> Hi,
> How are you declaring your classes to include from with in hiera?
>
> Is it similar to this?
>
> ---
> classes:
> - apache
> - apache::mod
> apache::someparamater: value
> apache::mod::php: blah
>
>
> If so, you should be able to do:
>
> ---
> classes:
> - apache
> - apache::mod::php
> apache::my_favorite_parameter: value
> apache::mod::php::php_parameter: some_other_vaule
>
> I haven't tried that exact thing with the apache module, but it does
> work for other modules with sub-classes that I've been working with.
> That is assuming that you're using the 'classes' array with the
> hiera_include function. We use the create_resources function to create
> wrappers for defines, while regular classes are included via the
> hiera_include and classes array.
>
> Our setup was pretty much taken directly from the hiera documentation:
>
>
> http://docs.puppetlabs.com/hiera/1/puppet.html#assigning-classes-to-nodes-with-hiera-hierainclude
>
>
> There are some gotchas that come up with the hiera merge behavior
> depending on how complex you're hiera layout becomes. For example, we
> had to set the hiera merge_behavior to deeper for us to get some of the
> desired results that we were looking for.
>
> --
> Joseph Swick <[email protected] <javascript:>>
> Operations Engineer
> Meltwater Group
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/b20be34f-afce-4c76-805c-fb9ca879ec0a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
