On Wednesday, February 26, 2014 2:47:32 PM UTC+1, nikolavp wrote: > What is the reason for the definition of those classes on the same host? >
That's because I have some more general "role A" to which some hosts belong, but I also have "role B" which is some sort of further specification of role A, and host B belongs to it and thus needs a more specific configuration file. > Can't it just be a single class with a parameter moved to hiera or Er... I never used hiera until now. I had a look at the doc but it seemed to me a bit overkill for this requirement. something else? My other suggestion would be to create a fact that > changes the setting on the machine based on the fact value. > Would be a good idea, but can a fact be created with a value which depends on puppet classes assigned to the host? Uhm... maybe assign the fact value based on the output of a command like "puppet resource user <someuser_created_only_on_host_b>"? I'm afraid the result would be based on existence on the master again, not on the agent. Thanks. -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7fdf4cc4-9c21-45ef-8afc-4884f927c81e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
