Merge pull request #690 from tpdownes/master

Allow user to modify loglevel of apt-get update Exec resource

diff --combined README.md
index 3168f518cb212451ed2db81e11d629adf68b04b9,bbe429fc9f8dfe015576903d252b2db066645257..98dcc2ce4fd6068b2cf92e1c93c8e58347ac953c
--- 1/README.md
--- 2/README.md
+++ b/README.md
@@@ -91,6 -91,15 +91,15 @@@ class { 'apt'
    },
  }
  ```
+ When `Exec['apt_update']` is triggered, it will generate a `Notice` message. Because the default [logging level for agents](https://docs.puppet.com/puppet/latest/configuration.html#loglevel) is `notice`, this will cause the repository update to appear in logs and agent reports. Some tools, such as [The Foreman](https://www.theforeman.org), report the update notice as a significant change. By setting the [loglevel](https://docs.puppet.com/puppet/latest/metaparameter.html#loglevel) metaparameter for `Exec['apt_update']` above the agent logging level, one can eliminate these updates from reports:
+ ```puppet
+ class { 'apt':
+   update => {
+     frequency => 'daily',
+     loglevel  => 'debug',
+   },
+ }
+ ```
  
  ### Pin a specific release
  
@@@ -160,7 -169,7 +169,7 @@@ include the `apt` class, which will pic
  hiera.
  
  ```yaml
 -apt::source:
 +apt::sources:
    'debian_unstable':
      comment: 'This is the iWeb Debian unstable mirror'
      location: 'http://debian.mirror.iweb.ca/debian/'