summaryrefslogtreecommitdiff
path: root/manifests/init.pp
AgeCommit message (Collapse)Author
2016-06-27push logic behind apt::repos back in apt::paramsGabriel Filion
The logic in specifying the default value for apt::repos is in the wrong place: it should be in apt::params since this is exactly what this latter class is for. There's no special case that can involve making default the value follow the value of another parameter so there's no point in having that logic in the main class.
2016-06-27make backports_url follow debian_url by defaultGabriel Filion
backports_url was already set to the same value than debian_url by default, but it was set to the default value of debian_url. this meant that when giving a url to the debian_url parameter to the apt class, the backports_url would not follow and would still be using the default value for debian_url. with this change, when backports_url is not specified, but debian_url is, then both of them take on the value given to the debian_url. of course if backports_url is also given a value, then it keeps the value given by the user.
2016-02-25Remove loglevel directive from Exec[update_apt]varac
When using puppet apply (v 3.7), loglevel 'info' won't show the output on error. This is bad for debugging.
2016-02-01[refactor] Get rid of the disable_update parametervarac
The `disable_update` parameter has been removed. The main apt class defaults to *not* run an `apt-get update` on every run anyway so this parameter seems useless. You can include the `apt::update` class if you want it to be run every time.
2016-02-01[feat] Remove `apt-get autoclean` from apt::updatevarac
`apt-get autoclean` should not be run on every puppetrun when including `apt::update`, but rather be configured as a `APT::Periodic` task that is run by cron, see https://wiki.debian.org/UnattendedUpgrades.
2016-02-01[refactor] Unify `apt-get update` into one resourcevarac
Before, there were two Execs that did an `apt-get update`, `Exec[refresh_apt]` and `Exec[apt_updated]`, which were triggered by different resources. This changes gets rid of the first one, and all resources now depend on `Exec[apt_updated]`.
2015-12-13[feat] Don't run an additional apt-get updatevarac
When adding custom keys, an additional `apt-get update` would be run before the Exec['refresh_apt'], which don't make sense.
2015-12-04remove requirement on lsb package for sources.list fileGabriel Filion
Managing requirements for installing the lsb package has proven over time to make no sense. The best approach to this is to require lsb-release to be installed alongside puppet, since otherwise there are so much facts that get no value during the run and you end up needing to run puppet twice to get the real end result. Also, since we're not including a class that is actually installing the 'lsb' package, that require line makes it so that including the apt module doesn't work, and there's no documentation in the README about needing to provide a package{'lsb':} resource with the apt class. Because of all that, it makes more sense to just get rid of that require line and mark lsb as a pre-requirement in the README file.
2015-12-04Simplify conditional expressionsJerome Charaoui
2015-12-04Switch old $release and $codename local variables to new debian_* factsJerome Charaoui
2015-12-04move backports to snippetsAntoine Beaupré
this allows for third party modules to enable this on the fly
2015-10-09Fix merge conflict in READMEJerome Charaoui
2015-06-09allow possibility of disabling backportsAntoine Beaupré
2015-05-11Replace debian_*() parser functions with factsJerome Charaoui
* Removes dependency on lsb-release and/or Facter >1.7 (values are based on $::lsbdistcodename, when available) * Simplifies maintenance: only lib/facter/util/* require updates as new releases are made Caveats: * apt::codename is removed; to override debian_* facts, set the FACTER_debian_codename environment variable for puppet * If tracking unstable, make sure lsb-release is installed, as other methods can't tell between testing and unstable
2015-02-28Add missing "include common::moduledir".intrigeri
Without this, $common::moduledir::module_dir_path is empty.
2015-02-20Merge branch 'master' of git://git.puppet.immerda.ch/module-aptJerome Charaoui
Conflicts: templates/Debian/sources.list.erb
2015-02-07Add support for Squeeze LTS.intrigeri
2014-01-08use the new style common modulemh
2013-07-27Make custom_sources_list into a class paramterGabriel Filion
and thus remove the last global variable.
2013-06-25Merge branch 'bug/fix_push' into leapMicah Anderson
This gets us fixes for the unattended_upgrades in wheezy, as well as the custom_key_dir class parameter replacement of the global variable Conflicts: manifests/unattended_upgrades.pp
2013-06-25Make custom_key_dir a class parameter and not a global variableSilvio Rhatto
Conflicts: manifests/init.pp
2013-05-26Merge branch 'master' into leapMicah Anderson
2013-03-20Move apt class parameters to a ::params class.intrigeri
This brings no behaviour change yet, but will allow to set class parameters' default value depending on system facts.
2013-03-14apt keys: always deploy before Exec[refresh_apt], also with $custom_preferencesdeploy_key_before_updatevarac
2013-03-05fix #4249: Ubuntu: wrong sources.list entriesvarac
2013-01-02Apply code style corrections from puppet-lintGabriel Filion
Signed-off-by: Gabriel Filion <lelutin@gmail.com> + more linting by intrigeri. Conflicts: manifests/apticron.pp manifests/cron/dist_upgrade.pp manifests/cron/download.pp manifests/dist_upgrade/initiator.pp manifests/init.pp manifests/listchanges.pp manifests/preferences.pp manifests/preseeded_package.pp manifests/proxy_client.pp manifests/unattended_upgrades.pp manifests/update.pp
2013-01-02Simplify codename handling.intrigeri
Have the codename class parameter default to $::lsbdistcodename, and derive $release from it.
2013-01-02Remove duplicated settings, resulting from wrong merge.intrigeri
2013-01-02Merge remote-tracking branch 'riseup/immerda_27_readme' into sharedintrigeri
Conflicts: README manifests/cron/dist_upgrade.pp manifests/cron/download.pp manifests/init.pp manifests/preferences.pp
2013-01-02Merge branch 'master' into issue_3953Gabriel Filion
2012-12-30Merge remote-tracking branch 'riseup/feature/http_debian_net'intrigeri
2012-12-30Merge remote-tracking branch 'riseup/feature/unknown_lsbdistcodename'intrigeri
2012-12-18On a sid system, $lsbdistcodename is reports 'n/a', this doesn't work ↵Micah Anderson
because the module looks for a template based on the $lsbdistcodename, so you get this error: Could not find template 'apt/Debian/preferences_n/a.erb' The slash in 'n/a' appears to be a path (confusing!) So I've set an error message when 'n/a' is encountered, encouraging the user to set the $lsbdistcodename. I was not confident in the idea of pointing any occurrence of 'n/a' to the sid templates, as I could imagine a case where this might occur on a non-sid system where the lsbdistcodename isn't properly detected
2012-12-18switch default $debian_url to use http.debian.net which is more accurate and ↵Micah Anderson
up-to-date than cdn.debian.net
2012-12-18added $apt_disable_update to disable "apt-get update" during puppetrunsnadir
2012-12-05fix for $lsbdistcodename regression introduced by ↵Micah Anderson
ac166366d7baa45b74e09974289d9fb2dad38e67 What happened here was the $codename = $::lsbdistcodename was removed from init.pp and replaced with just $::lsbdistcodename whereever $codename was used. Then in the sources.list.erb and preferences files things were changed like this: <pre>+### Debian current: <%= codename = scope.lookupvar('::lsbdistcodename') %> ... -deb <%= debian_url %> <%= codename %> <%= repos %> ... +deb <%= debian_url=scope.lookupvar('apt::debian_url') %> <%= codename %> <%= repos=scope.lookupvar('apt::repos') %> </pre> This meant that the codename was always set to lsbdistcodename, and you because in newer puppet versions you cannot assign a value to a top-level facter variable, it is not possible to change this. Because we cannot change $lsbdistcodename, we have to fix this by allowing the user to pass a different, non-top-level scoped variable to the class as a parameter, which defaults to $::lsbdistcodename, so that upgrades can be triggered. This is documented in the README in an upgrade notice
2012-09-20Make apt::preferences_snippet place files in /etc/apt/preferences.dGabriel Filion
Since Debian Squeeze, apt supports a .d directory for preferences (pinning). Simplify management by just placing files inside this .d directory. This removes the need for concat and concat::fragment resources, so removes the dependency on the concat module. It also removes the need for a moduledir that was needed for the concat module magic, so we also get rid of the dependency on the common module. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-09-20Stop using config_file from the common moduleGabriel Filion
This define doesn't add much of a shortcut and imposes a dependency on the "common" module. We'll be better off with the small repetition but less tightly coupled modules. Sadly, the "common" module is still required, but that is going to be the focus of the commit that follows this one. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-06-18get rid off config_file wrappermh
2012-06-14migrate away from hiera stuffmh
2012-06-08refactor things for >2.7mh
2012-06-08Migrate - in class names to _mh
In newer puppet releases the old way to name class/modules with a -, won't anymore be supported. Conflicts: manifests/unattended_upgrades.pp
2012-06-05new style for 2.7mh
2012-04-15Migrate - in class names to _mh
In newer puppet releases the old way to name class/modules with a -, won't anymore be supported.
2012-04-11use correct references for new concat usagemh
2012-04-09Force an apt-get update when changing an apt::sources_listGabriel Filion
sources_list doesn't currently force puppet to run 'apt-get update' after creating/modifying/removing files in sources.list.d. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-04-09Refactor: manage .d directories when using sources_list and apt_confGabriel Filion
The .d directories are only managed by the main 'apt' class. However, both 'sources_list' and 'apt_conf' defines depend on those directories. So in practice, the defines have an implicit need for those directories to be somehow managed. Let's turn this into an explicit relation, and include the directories in the defines. This makes it possible to use both defines without having to include the main 'apt' class. (maybe when using puppet apply?) Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2011-04-25Revert "apt::custom_sources_template to deploy custom sources.list.d/xyz.list"intrigeri
This reverts commit 3c0499b78d1f671fcce13127ef14b1b662a48c5a. This was already provided by sources_list.pp.
2011-01-09apt::custom_sources_template to deploy custom sources.list.d/xyz.listnadir
2010-12-15Repair Exec['update_apt'] to run apt-get update when needed.intrigeri
Move this Exec to a dedicated class that is not included by default i.e. we default not to "apt-get update" on every Puppet run. We now make use of this class in the apt::upgrade_package define to make sure APT indexes are up-to-date before attempting package upgrades. One may now use the following to ensure current packages are installed by Package resources: include apt::update Package { require => Exec[apt_updated] }