>
>
> It should be:
>
> ---
> classes:
> foobar:
>
>
>
I thought the {} might be the issue too, however that* is* valid YAML (my
ENC is a ruby script that just calls .to_yaml on a constructed hash). If
that's indeed the issue, I think
that should probably be considered a bug. I think whatever's taking the
output of the ENC should not get confused between a nil and an empty hash
(what happened to duck typing? :-))
I will try it tomorrow. However if I remember correctly (I was bogged down
with other things yesterday as well), I did try passing dummy parameters
too, e.g.
---
classes:
foobar:
foo: bar
... and this also did not work.
And thanks for the puppet node command! I did not know about that. I'll
give that a go as well
On Thursday, August 23, 2012 7:40:46 PM UTC-4, Nick Fagerlund wrote:
>
> Oh wait, also!
>
> On Thursday, August 23, 2012 1:12:03 PM UTC-7, Jon McKenzie wrote:
>>
>>
>> Is there a way on the server side to validate the ENC -> class
>> transformation for clients? I can see in the logs when the ENC script gets
>> run, but there's not much other detail
>>
>>
>>
> Yeah, get the node object at the command line on your puppet master.
>
> $ sudo puppet node find screech.magpie.lan --mode master --render-as yaml
>
> ...where screech.magpie.lan is the node name. It'll have a 'classes' key
> which will be either an array or a hash depending on how your ENC was
> rigged.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/vy0CAL46eE8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
