On Monday, July 21, 2014 9:20:59 AM UTC-5, Georg Brunmayr wrote: > > Hi folks, > > i work with puppet for some time now and usually find what i need to know > but here my google skills fail... > > What i'm doing is roughly this: > I have a pre and post stage where a node gets disabled in our build > system. This is done via a custom type that sets the attribute (some xml > handling) in the local file that is uploaded via another type that is just > there to do the upload on the client via ruby. > That works perfect now but as a result of that mechanism every run reports > at least 4 changes -> the dis-/enabling of the node via the attribute and > the upload of the file. > These reports are correct as i really changed something in there but as i > do these 4 changes on every run my dashboard view no longer shows just real > changes but these as well which makes it a lot harder to see when a change > was rolled out to the node. > > Does anybody have an idea how i can get rid of these reports? I want to > suppress just the changes for 1 attribute and the upload as all other > attribute changes should show up as changes. > Any ideas anyone? > >
Create a script wrapping a "puppet agent --onetime --no-daemonize" run, and perform the node disablement/re-enablement in that script. Instead of running the agent in daemon mode, use an external scheduler (e.g. cron) to run the wrapper script on whatever schedule you like. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/76cf2582-7cf9-47e5-ad96-828917126022%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
