apt v1.2.0, includes README updates for resolved tickets

apt/README.md

@@ -1,19 +1,23 @@
 Description
 ===========
 
-Configures various APT components on Debian-like systems.  Also includes a LWRP.
+This cookbook includes recipes to execute apt-get update to ensure the local APT package cache is up to date or manage apt-cacher and cacher clients. It also includes a LWRP for managing APT repositories in /etc/apt/sources.list.d.
 
 Recipes
 =======
 
 default
 -------
-The default recipe runs apt-get update during the Compile Phase of the Chef run to ensure that the system's package cache is updated with the latest. It is recommended that this recipe appear first in a node's run list (directly or through a role) to ensure that when installing packages, Chef will be able to download the latest version available on the remote APT repository.
+
+This recipe installs the `update-notifier-common` package to provide the timestamp file used to only run `apt-get update` if the cache is less than one day old.
+
+This recipe should appear first in the run list of Debian or Ubuntu nodes to ensure that the package cache is up to date before managing any `package` resources with Chef.
 
 This recipe also sets up a local cache directory for preseeding packages.
 
 cacher
 ------
+
 Installs the apt-cacher package and service so the system can provide APT caching. You can check the usage report at http://{hostname}:3142/report. The cacher recipe includes the `cacher-client` recipe, so it helps seed itself.
 
 cacher-client
@@ -23,7 +27,7 @@ Configures the node to use the apt-cacher server as a client.
 Resources/Providers
 ===================
 
-This LWRP provides an easy way to manage additional APT repositories.
+This LWRP provides an easy way to manage additional APT repositories. Adding a new repository will notify running the `execute[apt-get-update]` resource.
 
 # Actions
 
@@ -40,7 +44,7 @@ This LWRP provides an easy way to manage additional APT repositories.
 - key_server: the GPG keyserver where the key for the repo should be retrieved
 - key: if a `key_server` is provided, this is assumed to be the fingerprint, otherwise it is the URI to the GPG key for the repo
 
-# Example
+# Examples
 
     # add the Zenoss repo
     apt_repository "zenoss" do
@@ -86,6 +90,15 @@ The above will run during execution phase since it is a normal template resource
 
 Put `recipe[apt::cacher]` in the run_list for a server to provide APT caching and add `recipe[apt::cacher-client]` on the rest of the Debian-based nodes to take advantage of the caching server.
 
+Changes
+=======
+
+## v1.2.0:
+
+* COOK-136: Limit apt-get update to one run per day unless notified.
+* COOK-471: ignore failure on apt-get update
+* COOK-533: add support for deb and `deb_src` repos with `apt_repository`
+
 License and Author
 ==================
 

apt/metadata.rb

@@ -3,7 +3,7 @@
 license           "Apache 2.0"
 description       "Configures apt and apt services and an LWRP for managing apt repositories"
 long_description  IO.read(File.join(File.dirname(__FILE__), 'README.md'))
-version           "1.1.2"
+version           "1.2.0"
 recipe            "apt", "Runs apt-get update during compile phase and sets up preseed directories"
 recipe            "apt::cacher", "Set up an APT cache"
 recipe            "apt::cacher-client", "Client for the apt::cacher server"