Puppet force yum update

Boolean value. Defaults to true. Please read Puppet cron type. Mode in which yum-cron should perform. Valid values are check , download and apply. Defaults to apply. Enable email notifications. Recipient email address for update notifications. Defaults to root local user An empty string forces the output to stdio, so emails will be sent by crond.

Sender email address for update notifications. Defaults to root local user Note: not supported on CentOS 5. YUM debug level. Valid values are numbers between -1 and YUM error level. Valid values are numbers between 0 and Defaults to 0 Note: always outputs to stdio on modern platforms, can apparently not be changed.

Maximum amount of time in minutes YUM randomly waits before running. Day s of the week that the update job should run, specified as an array.

Default: [''] weekdays only. Only works on systems that use Yum for package management. PuppetEcosystem Puppet Community Updates. Any Supported Supported or Approved. Operating system Any. With tasks? Any Yes. Puppet module to handle Yum updates. Module Stats 9, downloads 6, latest version 4. Version information 0. This version is compatible with: Puppet Enterprise Start using this module.

Installation method r10k or Code Manager. Add this module to your Puppetfile: mod 'jgazeley-yumupdate', '0. Add this module to your Bolt project: bolt module add jgazeley-yumupdate. So, you are looking at close to about 4 days from start to finish. This may be excessive for your organization, or it may need to be longer. However you approach it, keep a sprinkle of sanity in the mix. The implementation is actually quite simple, really. In the example below, the updates will run on the 6th of every month between am and am.

Consider that the next step of evolution. However you choose to proceed is up to you. Automation is king here. Understand, though, that it also makes your puppet server that much more critical, and making a mistake here can have a much wider impact.

Hence, I stress the testing period and having someone on-hand for the final phases. Once the level of comfort grows with the process, you may want to implement more automation based upon your individual environment eg: rebooting development machines might be fine at your organization.

Maintain Your Own Repositories This cannot be highlighted enough. There's no need to keep syncing the OS repo as that never changes. Rebuild the repository data for EPEL. Rebuild the repository data for RHEL.