On Sunday, July 13, 2014 10:47:26 AM UTC-5, Taylor Leese wrote: > > The work around I went with is to just avoid the "require 'puppet'" line > in my external node classifier so I can avoid this issue completely. I just > ignore the first line of the YAML file in /var/lib/puppet/yaml/facts/ and > do YAML.load rather than YAML.load_file. >
I'm glad you found a solution. It's not clear to me why "require 'puppet'" would cause your ENC to fail, but one possibility would be that your Puppet install is not in the default Ruby load path. That seems especially likely if the behavior can be toggled just by the 'require', without actually using anything thereby loaded. On the other hand, I'm inclined to think that your ENC probably *should* avoid requiring Puppet if it reasonably can do, so I wouldn't change anything from what you have now. John -- 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/a36c7e97-6150-46e8-86c5-dd99cb661e44%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
