X-Git-Url: https://review.fuel-infra.org/gitweb?a=blobdiff_plain;f=README.md;h=b0574a7aa0a138adbb9b536c79a0ef13f828fd37;hb=1e1f61a636b6432622af25c8c9e190de7d5a8370;hp=c7938a6a880879e875e204ab72f8fa8bb365b90e;hpb=483a0f86ab48fe7d799a44f0023e8fef6a193b7f;p=puppet-modules%2Fpuppetlabs-apt.git diff --git a/README.md b/README.md index c7938a6..b0574a7 100644 --- a/README.md +++ b/README.md @@ -48,6 +48,7 @@ The parameters for `apt` are not generally required and are predominantly for de class { 'apt': always_apt_update => false, + apt_update_frequency => undef, disable_keys => undef, proxy_host => false, proxy_port => '8080', @@ -153,9 +154,9 @@ Moreover, when Puppet is told to hold a package, it holds it at the current vers At first glance, it seems this issue could also be solved by passing the version required to the ensure attribute---but that only means that Puppet will install that version after it processes the package. It does not inform apt that we want -this package to be held; that is, should another package want to upgrade this one (because of a version requirement in a dependency, for example), we want apt to refuse. +this package to be held; that is, should another package want to upgrade this one (because of a version requirement in a dependency, for example), we want apt to refuse. -To solve this issue, use apt::hold. Implement this by creating a preferences file with a priority of 1001. Under normal circumstances, this preference will always win. Because the priority is > 1000, apt will maintain the required version, downgrading the current package if necessary. +To solve this issue, use apt::hold. Implement this by creating a preferences file with a priority of 1001. Under normal circumstances, this preference will always win. Because the priority is > 1000, apt will maintain the required version, downgrading the current package if necessary. With this, you can now set a package's ensure attribute to 'latest' but get the version specified by apt::hold: @@ -211,7 +212,7 @@ If you would like to configure your system so the source is the Puppet Labs APT ### apt::update -Runs `apt-get update`, updating the list of available packages and their versions without installing or upgrading any packages. +Runs `apt-get update`, updating the list of available packages and their versions without installing or upgrading any packages. The update runs on the first Puppet run after you include the class, then whenever `notify => Exec['apt_update']` occurs---this should happen when config files get updated or other relevant changes occur. If you set the `always_apt_update` parameter, the update will run on every Puppet run. @@ -222,6 +223,7 @@ There are a few facts included in the apt module describing the state of the apt * `apt_updates` --- the number of updates available on the system * `apt_security_updates` --- the number of updates which are security updates * `apt_package_updates` --- the package names that are available for update. In Facter 2.0 and later, this will be a list type; in earlier versions, it is a comma-delimited string. +* `apt_update_last_success` --- The date in epochtime that `apt-get update` last ran successfully. This is determined by reading the mtime of the file `/var/lib/apt/periodic/update-success-stamp`. That file is generated by the `/etc/apt/apt.conf.d/15update-stamp` file. #### Hiera example
@@ -332,3 +334,4 @@ A lot of great people have contributed to this module. A somewhat current list f
 * Zach Leslie 
 * Daniele Sluijters 
 * Daniel Paulus 
+* Wolf Noble