rismoney
commented
8 years ago Nothing package specific, because puppet creates a catalog of all resources and dependencies. You can stop the service, and then using scheduled tasks call the puppet agent via a script.
In my environment we have strict requirements to not run puppet during operating hours, and instead orchestrate puppet runs. You could probably do this via powershell remoiting, mcollective or perhaps by way of some new orchestration engine puppetlabs is serving up or other tooling.
If your puppet agent runs are taking 30 minutes I would question what it is doing. Unless you mean you are running it on 30 minute intervals.
Hi,
Is it possible to implement a feature that allows us to set up different schedules for installing and updating packages with Puppet?
We have >100 windows boxes, all of them is running Puppet and have Chocolatey. We don't want Puppet to check Chocolatey package updates on each run (which is 30 minutes by default), only let's say once a day. However, we also want Puppet + Chocolatey to install new packages on the next run.
We know Puppet has a schedule resource and metaparameter, but if we use that, we can't achieve installing newly defined packages on the next Puppet run.
Thank you. Zoli