It looks like your doing parameter validation the old fashioned way. So there is no reason to have complicated validation code when it can be done easier using parameter data types and runtime validation. The easiest way is to validate $ensure is to use data types like Enum. Check out the data type feature in the future parser which would negate the need to use the conditional logic in your original example. Another way without using the future parser would be to use stdlib validate_XX functions.
https://docs.puppetlabs.com/puppet/4.3/reference/lang_data_abstract.html#enum Example class class foo(Enum['present', 'absent'] $ensure = 'present'){ file{'/tmp/foo.txt': ensure => $ensure, content => 'bar' } } Corey On Tuesday, November 24, 2015 at 3:03:04 PM UTC-5, Matthew Ceroni wrote: > > Working on migrating my manifests to work with Puppet 4.0. Currently on > 3.8 and have started to experiment with the future parser (probably not so > much future anymore). > > I am stuck on an error that is being reported. > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Evaluation Error: Error while evaluating a Function Call, ensure parameter > must be specified at > /etc/puppet/environments/sandbox/modules/sudo/manifests/init.pp:51:2 on > node op1227 > > The code is a simple check and fail if not met > > if ! ($ensure in [ 'present', 'absent' ]) { > fail("sudo 'ensure' parameter must be set to either 'absent' or > 'present'") > } > > It isn't liking something about the function call fail. > > Any help would be appreciated. > > 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/b00b1faf-13cb-46ff-83e4-b60205fe45e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
