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
> will likely add another) and I'm quickly realizing that building logic in
> the manifest to deal with the differences in Red Hat i386 vs Red Hat x86_64
> vs SuSE i586 vs SuSE x86_64 vs Mac is getting tedious. For instance, in the
> sshd_config:
>
> SLES i586 has the sftp-server binary in a different path than the x86_64
> version and it's different than RHEL - so I end up with logic as such:
>
> # Set the SFTP Path
> if $lsbdistid == 'SUSE LINUX' {
> if $architecture == 'x86_64' {
> $sftppath = '/usr/lib64/ssh/sftp-server'
> } else {
> $sftppath = '/usr/lib/ssh/sftp-server'
> }
> } else {
> $sftppath = "/usr/libexec/openssh/sftp-server"
> }
>
>
> Is there a better way to deal with different OS's or is the long and
> winding road of config mgmt?
>
> Do people do something like:
>
> include ssh::server::$operatingsystem
>
> class ssh::server::RedHat {
> blah
> }
>
> class ssh::server::SLES {
> blah
> }
>
>
> Different modulepath? Different puppet servers based on OS?
>
> Cheers,
>
> Jeff
>
--
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/55a8b25b-a8c3-400d-911f-2864cc2c4428%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
