Data in Modules: Fail on unsupported OS

[plapp...@gmail.com]

Good morning :)

I'm currently writing a puppet module for the OpenBSD specific implementation of SNMPd, and was wondering if there is any elegant way  for the module to fail on unsupported operating systems?

With the params.pp-pattern, you can fail as the default of the OS-specific configuration; but how would I do this with the data comes via Hiera from the module itself (https://docs.puppet.com/puppet/4.10/hiera_migrate_modules.html#module-data-with-yaml-data-files)? 

Of course I can simply leave the common.yaml empty and the module will fail with missing variables, but I'd rather have a helpful error message about an unsupported OS (which will be less confusing, should this module be used by someone else but me).

Kind regards, 

Jake

[Henrik Lindberg]

How about setting a value that represents a "poison pill" as the default
(for example "not supported"). Then for all supported the value would be
something other than the "poison pill". You then check if you got the
"poison" and then error with a descriptive error message.


- henrik
--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

[Michael Watters]

I usually do this within the manifest itself.  For example:

if $facts['osfamily']!='RedHat'{fail("$operatingsystem is not supported")}