X-Git-Url: https://review.fuel-infra.org/gitweb?a=blobdiff_plain;f=README.md;h=98dcc2ce4fd6068b2cf92e1c93c8e58347ac953c;hb=a06eece5526b8838bcdd0a5f9b649b95727e09d7;hp=ac945b40933428c3aaeb32a8021fd92664d48563;hpb=09fe368ae25afca684b75e87d81486252ccb6822;p=puppet-modules%2Fpuppetlabs-apt.git

diff --git a/README.md b/README.md
index ac945b4..98dcc2c 100644
--- a/README.md
+++ b/README.md
@@ -91,6 +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 @@ include the `apt` class, which will pick up the values automatically from
 hiera.
 
 ```yaml
-apt::source:
+apt::sources:
   'debian_unstable':
     comment: 'This is the iWeb Debian unstable mirror'
     location: 'http://debian.mirror.iweb.ca/debian/'