On Jul 15, 2009, at 1:24 AM, Dan Bode wrote:
> For my use case, I have set the following in puppet.conf on the agent
>
> [puppetd]
> noop=true
>
> on the server, in the puppet module, I set the following:
>
> file{"/etc/puppet/puppet.conf":
> noop => false,
> content => template("puppet/puppet-agent.conf"),
> }
>
> I have noticed that this works, noop effects everything except the
> puppet.conf file, here is some output
>
> notice: Starting catalog run
> notice: //Node[SERVER]/test/Exec[echo "This is the Test Class"]/
> returns: is notrun, should be 0 (noop)
> 39c39
> < # TEST1
> ---
> > # TEST2
> notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]:
> Filebucketed to main with sum 612edd1118e135cdd89675c1c8f981ae
> notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]/
> content: content changed '{md5}612edd1118e135cdd89675c1c8f981ae' to
> '{md5}14ce20b1d2499bed640a26e051a52909'
> notice: Reparsing /etc/puppet/puppet.conf
>
> My question is:
>
> Is this intended behavior, will this be supported in future
> versions, or will this be likely to break.
That's your own code managing puppet.conf, not puppet, so yeah, that
will continue to work.
--
Barondes' First Law:
Science abhors contradictions; scientists' minds are replete with
them.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
