On Wednesday, April 18, 2012, Chris Donovan wrote: > Hi, > > Yes, filename is what is supposed to be there. That's not my issue > however though, my issue is that it doesn't load / run properly. > > If puppet 2.7.6 still does not run functions on the client then that's > great, and I'll write a provider, and possibly a type. > > Puppet only executes functions on the master - that's by design. Custom facts are executed in the client.
You might want to look at the file_line type ( https://github.com/puppetlabs/puppetlabs-stdlib/blob/11156fd29a6ccee64663a5a32cf0b37d1867cfb0/lib/puppet/type/file_line.rb) or Augeas to modify lines in a file. > Chris- > > On Thu, Apr 19, 2012 at 1:21 PM, Gary Larizza > <g...@puppetlabs.com<javascript:;>> > wrote: > > At first glance (on phone), Check this line: > > > > file = File.open(file, 'r+') > > > > > > Don't you want filename as the argument? > > > > > > n Wednesday, April 18, 2012, Chris Donovan wrote: > >> > >> Hello, > >> > >> So I'm working my way through writing custom functions for puppet 2.7.6, > >> and what I think is valid seems not to be, and unfortunately I can't > find > >> any additional help in the docs. I've got a pastebin link > >> (http://pastebin.com/HimPyWHh) that shows my function, site.pp, and > the file > >> I'm trying to manipulate with my function. It's fairly basic as you can > >> tell. > >> > >> I'm getting the following error from the client: err: Could not retrieve > >> catalog from remote server: Error 400 on SERVER: can't convert nil into > >> String at /etc/puppet/manifests/site.pp:81 on node thing > >> I've been through the troubleshooting stages, ruby -rpuppet > fileModify.rb, > >> irb etc. and those work fine. > >> > >> If I make a syntax error in the function, puppet quite happily complains > >> about it, so it can certainly read the function file. > >> > >> any suggestions? questions? help? :) > >> ohh, and I'm following this guide here: > >> http://docs.puppetlabs.com/guides/custom_functions.html > >> > >> > >> Chris- > >> > >> -- > >> 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/-/Fd-wqOv1dBIJ. > >> To post to this group, send email to > >> puppet-users@googlegroups.com<javascript:;> > . > >> To unsubscribe from this group, send email to > >> puppet-users+unsubscr...@googlegroups.com <javascript:;>. > >> For more options, visit this group at > >> http://groups.google.com/group/puppet-users?hl=en. > > > > > > > > -- > > > > Gary Larizza > > Professional Services Engineer > > Puppet Labs > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to > > puppet-users@googlegroups.com<javascript:;> > . > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com <javascript:;>. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to > puppet-users@googlegroups.com<javascript:;> > . > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com <javascript:;>. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- Gary Larizza Professional Services Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.