This is pretty much exactly what module data is for. Check
out https://docs.puppet.com/puppet/4.9/lookup_quick_module.html for more
details.
On Friday, September 30, 2011 at 2:33:50 PM UTC-4, Jeff Falgout wrote:
>
> We're in the situation of dealing with multiple operating systems (and
>
On 2/24/17 5:30 PM, Nate B wrote:
> // , Is there a better way to deal with this in later versions of Puppet?
>
> I lean toward using different manifests for different operating system
> variations, but like the original poster says, no matter how one
> organizes the logic, it still gets
You can build agnostic code in Puppet and pull operating system specifics
from Hiera. For example:
#ls -l hieradata/
total 4
-rw-r--r-- 1 root root 872 Feb 12 18:28 common.yaml
drwxr-xr-x 1 root root 0 Feb 28 12:31 nodes
drwxr-xr-x 1 root root 68 Feb 28 12:31 os
#ls -lR hieradata/os
// , Is there a better way to deal with this in later versions of Puppet?
I lean toward using different manifests for different operating system
variations, but like the original poster says, no matter how one organizes
the logic, it still gets tedious.
Puppet 4.9 doesn't even seem to have
