The rationale expressed to me has to do with non-specific auditing/security requirements...
My requirement is to research and contradict with prima face evidence or report and confirm or some mixture thereof, which is not the simplest of assignments. If anyone at Puppet Labs and the community can think of a way to contradict the first paragraph, send it over. Stuart P.S. Thanks for your input that puppet agent need not be a daemon and can be run with: puppet agent -t --noop I will put that in place tomorrow. On Dec 2, 2013, at 3:52 PM, Rich Burroughs <r...@richburroughs.com> wrote: > Hi Stuart, > > I'm not sure what your use case is for running the agent as a daemon in noop > mode? I can't think of a situation at least in my workplace when I'd want to > do that. > > You know that you can run the agent once in noop mode from the command line? > You can do that without changing any configs really easily: > > puppet agent -t --noop > > We do that a lot where I work when we're testing code. The agent just runs > once and will report on what it would have done, but won't make any changes. > A lot of times when we test that we're doing it on a different git branch, > and we use "--environment=" to run against that other branch. > > I'm not sure if this is helpful, maybe you already know about it :) > > > Rich > > > > On Tue, Nov 26, 2013 at 5:07 PM, Stuart Cracraft <smcracr...@gmail.com> wrote: > What I had to do (confirm or deny at-will please) is: > > uncomment the node in /etc/puppet/manifests/nodes.pp > > on the puppet master > > and > > on the daemon have > > noop = true > > in the main section of the puppet.conf > > and run the agent simply as /usr/bin/ruby /usr/bin/puppet agent --verbose > > Now the yaml's get generated, have the message indicating what would be > changed > but don't change it at all. > > And we get "Would have triggered 'refresh' from N events in the > /var/log/messages on > the node. > > The only betterment to the above would be that /var/log/message over on the > puppet master. > > Desirable and controllable!!!! > > Stuart > > > On Tuesday, November 26, 2013 4:30:14 PM UTC-8, Stuart Cracraft wrote: > Hi, > > When I put > > noop = true > > in /etc/puppet/puppet.conf > > on the node in question, I observe no changes. Great. Good > > But also, I see because of > > report = true > > absolutely zero information in the yaml regarding what would have > been changed. > > Is there an equivalent to the above for "test = true" or must I alter > the rc file to include --test ? > > Thanks ahead Puppet wizards!!! > > > > -- > 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/3b0f53bf-7d5d-4094-8a26-fe975a1e6f17%40googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/0vhLrU0Rl_0/unsubscribe. > To unsubscribe from this group and all its topics, 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/CAPGcbtCN5ovzMjx2ii0CVaFdzsr2_y%2BVD4JQ%3D3jPiMQF0pnH1Q%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/2F378B74-1B2E-4B10-9D54-D9EA5C30335A%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
