summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
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-02Merge branch 'unatt_upg_logdir' into 'master' varac
Manage unattended-upgrades log directory In some situations, the log directory for unattended-upgrades might not exist. In those cases, packages will not get upgraded! unattended-upgrades crashes with a python backtrace because the log dir is not present. See merge request !38
2016-02-02Manage unattended-upgrades log directoryGabriel Filion
In some situations, the log directory for unattended-upgrades might not exist. In those cases, packages will not get upgraded! unattended-upgrades crashes with a python backtrace because the log dir is not present.
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]`.
2016-01-05[bug] Deploy preferene snippets before apt_refreshvarac
When pinning packages with apt::preferences_snippet, we need to make sure these get deployed before an `apt-get update` is triggered, so pinned packages can get installed in the right way with a single puppetrun.
2015-12-20[tests] Use beaker+docker for acceptance testsvarac
Beaker together with docker is a very fast way to do acceptance testing. This commit adds basic beaker/docker support: - Add a debian jessie nodeset - Test if the module applies idempotentially, so it doesn't change resources on a second run with the same parameters. https://github.com/puppetlabs/beaker/blob/master/docs/Docker-Support.md
2015-12-20Merge branch 'gitlab_ci' into 'master' Micah
[feat] Enable gitlab CI builds, simplify Gemfile Test this module using existing rspec test, using gitlab CI on gitlab.com shared runners. See https://gitlab.com/varac/apt/builds/473836 for the CI build of this merge req. See merge request !33
2015-12-19[feat] Enable gitlab CI builds, simplify Gemfilevarac
2015-12-16Merge branch 'remove_double_apt_get_update' into 'master' ng
[feat] Don't run an additional apt-get update When adding custom keys, an additional `apt-get update` would be run before the Exec['refresh_apt'], which don't make sense. See merge request !31
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-07Fix require path for ubuntu_nextcodename.rbvarac
2015-12-07[rspec] extend test for custom factsvarac
2015-12-07[bug] Fix debian_nextcodename on wheezy hostsvarac
I noticed this behaviour because $::debian_nextcodename was "squeeze" on a wheezy host. For debugging, i inserted a "puts codenames" in lib/facter/debian_nextcodename.rb, and it turned out that it was sorted differently on wheezy and jessie hosts: On wheezy: buster stretch jessie wheezy squeeze lenny On jessie: lenny squeeze wheezy jessie stretch buster So i decided to rewrite this so this doesn't happen again.
2015-12-07[docs] Add test docs how to use custom facter/puppet versionvarac
2015-12-07Fix loading of util/debian.rb for custom factsvarac
requirering the facter/util/debian.rb module causes puppet warnings on wheezy hosts, and custom facts like `$::debian_codename` cannot be evaluated. warning: Could not load fact file /srv/dev/projects/puppet/shared-modules//apt/lib/facter/debian_nextcodename.rb: no such file to load -- facter/util/debian Removing the require line solves this.
2015-12-07Add inital puppet rspec test for custom factsvarac
2015-12-04Merge branch 'support_missing_ubuntu_releases' into 'master' Micah
[feat] Support vivid, wily, xenial ubuntu release See merge request !27
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-12-04Use $ubuntu_url as default value of $backports_url on UbuntuGabriel Filion
Ubuntu shouldn't be using debian backports by default. This was written by Anoine Beaupré, but split from the commit "move backports to snippets" since the change is unrelated and needs to be more visible in the commit history.
2015-11-02[feat] Support vivid, wily, xenial ubuntu releasevarac
2015-10-09Document the new config_template parameterGabriel Filion
Also add an example for how to use the apt::unattended_upgrades class.
2015-10-09Make it possible to specify own template.Gabriel Filion
Micah found an issue with usage of config_content: if you call template('...') yourself and pass that on to config_content, then your template gets evaluated without all of the variables. This means that you don't hava access to blacklisted_packages, mail_recipient or mailonlyonerror. To make it possible to use a different template while still having access to those variables, let's make it possible to change the template name that we're using.
2015-10-09Fix debian_codename fact when falling back to parsing /etc/debian_versionJerome Charaoui
2015-10-09Improve unattended-upgrades origin selectorsJerome Charaoui
* On squeeze, use release fact instead of hardcoded release name * On wheezy, special-case because codename selector is not available * On jessie and up, start pulling in point-release updates. The codename selector ensures that we won't be upgrading to a new release automatically.
2015-10-09Fix merge conflict in READMEJerome Charaoui
2015-10-07Merge Debian squeeze, wheezy, jessie and sid preferences templates into oneJerome Charaoui
2015-10-03Extraneous copy of license fileGabriel Filion
GPLv3 was already applied 3 years ago to this code base. See LICENSE file.
2015-09-14Merge remote-tracking branch 'shared/key' into shared-master (!17)intrigeri
2015-08-31reboot_required_notify: add initial support for Jessie and newer.intrigeri
Note that reboot-notifier is only in stretch/sid at the moment, so to use this one needs to configure APT pinning themselves to make this package installable.
2015-08-31reboot_required_notify::wheezy: add an "ensure" parameter, defaulting to ↵intrigeri
"present".
2015-08-31reboot_required_notify: move all code to a ::wheezy class.intrigeri
It doesn't work on Jessie and newer (#1).
2015-08-31Add validation for apt::key's name.intrigeri
It's great to document requirements in README, but error'ing out whenever the user messes up is even better IMO.
2015-08-31Quote apt-key variable parameter.intrigeri
This is not perfect protection against special chars that the shell may interpret, but should help at least in case $name contains spaces.
2015-08-31Linting.intrigeri
2015-08-31Merge remote-tracking branch 'shared/key' into tmpintrigeri
2015-08-26document the .gpg extension requirementAntoine Beaupré
2015-08-26fix install location of apt::key::plainAntoine Beaupré
2015-08-26fix typoAntoine Beaupré
2015-06-11fix typoAntoine Beaupré
2015-06-11allow for binary keys that can be removedAntoine Beaupré
2015-06-11add apt::key resource to deploy arbitrary keysAntoine Beaupré
the rationale of this is that isn't useful for third party modules, because they cannot inject keys in there without some serious apt class hijacking
2015-06-09Merge branch 'volatile-backports' into 'master'Jerome Charaoui
allow disabling backports (and volatile in ubuntu) as the module stands now, there's no way to disable backports. there are a few reasons why we want to allow this: * "tools, not policy" - if Debian doesn't ship with backports enabled by default, why should we change that policy? * too many sources.list entries can cause problems on `apt-get update`, which can run out of memory and require special config * if the pinning fails, some packages may be updated by mistake * even if pinning works, some may *want* to keep admins from installing anything from backports as a policy this keeps backports installed by default (begrudgingly) however. it just allows disabling it. it also allows disabling volatile in ubuntu, which wasn't possible before. See merge request !16
2015-06-09also disable volatile on ubuntu if relevantAntoine Beaupré
2015-06-09also control backports on ubuntuAntoine Beaupré
2015-06-09typoAntoine Beaupré