Releases: voxpupuli/puppet-patching_as_code
Releases · voxpupuli/puppet-patching_as_code
Release list
Release 0.7.10
Improvements
- Allow reinstalls of KB4052623 as these are also monthly AV definition updates
Release 0.7.9
Bugfixes
- Correct KB2267202 to KB2267602
Release 0.7.8
Improvements
- Allow reinstalls of KB2267202 and KB2461484 as these are monthly AV definition updates
Release 0.7.7
Bugfixes
- Removed a dependency on the
patching_as_code_configfact inside of theis_patchday()function, preventing possible catalog compilation failures as a result of thepatching_as_code_configfact not yet existing for new agents.
Release 0.7.6
Bugfixes
- Account for the
patching_as_code_utc_offsetfact to be empty in some situations
Release 0.7.5
Improvements
- Now correctly adjusts for timezone differences between the Puppet Server and the managed node, ensuring that the local node time & date gets used to calculate if today is patch day.
- Now logs messages in the Puppet Server log to report the calculated local node time & day, as well as whether or not today is patch day for the node.
Release 0.7.4
Bugfixes
- Fixes a missing
schedulemetaparameter for theNotify[Patching as Code - Update Fact], which would cause thepe_patchfact to update at every Puppet run during the patch day, instead of only during the maintenance window.
Release 0.7.3
Release 0.7.3
Bugfixes
- Correctly handles package declarations where the title of the package resource does not match the name of the package.
Release 0.7.2
Improvements
- The pre-patch reboot in case of any pending reboots now happens also if it is patchday but there are no patches to install. This facilitates parallel patching tools to have installed patches before Puppet's patch window, with Puppet performing the actual reboot.
Note: The reboot still happens during the configured maintenance window.
Release 0.7.1
Improvements
- Adopted the
eval_generatefunction in thepatch_packagetype to ensure that newly generatedpackageresources become children of thepatching_as_code::linux::patchdayclass. This provides better context for these package resources, which can be leveraged in external reporting tools (e.g. Splunk). - Simplified the
patch_packagetype, removed capabilities that are no longer needed - Moved the logic to trigger the patch fact refresh to the main manifest
- Simplified the patchday classes