Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

apt

Puppet Labs Apt Module
Project URLRSS FeedReport issues

33,860,267 downloads

347 latest version

3.1 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 10.0.0 (latest)
  • 9.4.0
  • 9.3.0
  • 9.2.0
  • 9.1.0
  • 9.0.2
  • 9.0.1
  • 9.0.0
  • 8.5.0
  • 8.4.1
  • 8.4.0
  • 8.3.0
  • 8.2.0
  • 8.1.0
  • 8.0.2
  • 8.0.1
  • 8.0.0
  • 7.7.1
  • 7.7.0
  • 7.6.0
  • 7.5.0
  • 7.4.2
  • 7.4.1
  • 7.4.0
  • 7.3.0
  • 7.2.0
  • 7.1.0
  • 7.0.1
  • 7.0.0
  • 6.3.0
  • 6.2.1
  • 6.2.0
  • 6.1.1
  • 6.1.0
  • 6.0.0
  • 5.0.1
  • 5.0.0
  • 4.5.1
  • 4.5.0
  • 4.4.1
  • 4.4.0
  • 4.3.0
  • 4.2.0
  • 4.1.0
  • 4.0.0
  • 3.0.0
  • 2.4.0
  • 2.3.0
  • 2.2.2
  • 2.2.1
  • 2.2.0
  • 2.1.1
  • 2.1.0
  • 2.0.1
  • 2.0.0
  • 1.8.0
  • 1.7.0
  • 1.6.0
  • 1.5.2
  • 1.5.1 (deleted)
  • 1.5.0
  • 1.4.2
  • 1.4.1 (deleted)
  • 1.4.0
  • 1.3.0
  • 1.2.0
  • 1.1.1
  • 1.1.0
  • 1.0.1
  • 1.0.0
  • 0.0.4
  • 0.0.3
  • 0.0.2 (deleted)
  • 0.0.1 (deleted)
released Oct 28th 2014
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet 3.x
  • ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'puppetlabs-apt', '1.7.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add puppetlabs-apt
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install puppetlabs-apt --version 1.7.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download
Tags: debian, apt, ubuntu, dpkg, ppa, apt-get, aptitude

Documentation

puppetlabs/apt — version 1.7.0 Oct 28th 2014

apt

Build Status

Overview

The apt module provides a simple interface for managing Apt source, key, and definitions with Puppet.

Module Description

The apt module automates obtaining and installing software packages on *nix systems.

Note: While this module allows the use of short keys, we urge you NOT to use short keys, as they pose a serious security issue by opening you up to collision attacks.

Setup

What apt affects:

  • Package/service/configuration files for Apt
  • Your system's sources.list file and sources.list.d directory
  • System repositories
  • Authentication keys

Note: Setting the apt module's purge_sources_list and purge_sources_list_d parameters to 'true' will destroy any existing content that was not declared with Puppet. The default for these parameters is 'false'.

Beginning with apt

To begin using the apt module with default parameters, declare the class with include apt.

Any Puppet code that uses anything from the apt module requires that the core apt class be declared.

Usage

Using the apt module consists predominantly of declaring classes and defined types that provide the desired functionality and features. This module provides common resources and options that are shared by the various defined types in the apt module, so you must always include this class in your manifests.

class { 'apt':
  always_apt_update    => false,
  apt_update_frequency => undef,
  disable_keys         => undef,
  proxy_host           => false,
  proxy_port           => '8080',
  purge_sources_list   => false,
  purge_sources_list_d => false,
  purge_preferences_d  => false,
  update_timeout       => undef,
  fancy_progress       => undef
}

Reference

Classes

  • apt: Main class, provides common resources and options. Allows Puppet to manage your system's sources.list file and sources.list.d directory, but it does its best to respect existing content.

    If you declare your apt class with purge_sources_list, purge_sources_list_d, purge_preferences and purge_preferences_d set to 'true', Puppet will unapologetically purge any existing content it finds that wasn't declared with Puppet.

  • apt::backports: This class adds the necessary components to get backports for Ubuntu and Debian. The release name defaults to $lsbdistcodename. Setting this manually can cause undefined and potentially serious behavior.

    By default, this class drops a pin-file for backports, pinning it to a priority of 200. This is lower than the normal Debian archive, which gets a priority of 500 to ensure that packages with ensure => latest don't get magically upgraded from backports without your explicit permission.

    If you raise the priority through the pin_priority parameter to 500---identical to the rest of the Debian mirrors---normal policy goes into effect, and Apt installs or upgrades to the newest version. This means that if a package is available from backports, it and its dependencies are pulled in from backports unless you explicitly set the ensure attribute of the package resource to installed/present or a specific version.

  • apt::params: Sets defaults for the apt module parameters.

  • apt::release: Sets the default Apt release. This class is particularly useful when using repositories that are unstable in Ubuntu, such as Debian.

    class { 'apt::release':
  release_id => 'precise',
}

  • apt::unattended_updates: This class manages the unattended-upgrades package and related configuration files for Ubuntu and Debian systems. You can configure the class to automatically upgrade all new package releases or just security releases.

    apt::unattended_upgrades {
  origins             = $::apt::params::origins,
  blacklist           = [],
  update              = '1',
  download            = '1',
  upgrade             = '1',
  autoclean           = '7',
}

  • apt::update: Runs apt-get update, updating the list of available packages and their versions without installing or upgrading any packages. The update runs on the first Puppet run after you include the class, then whenever notify => Exec['apt_update'] occurs; i.e., whenever config files get updated or other relevant changes occur. If you set the always_apt_update parameter to 'true', the update runs on every Puppet run.

Types

  • apt_key

    A native Puppet type and provider for managing GPG keys for Apt is provided by this module.

    apt_key { 'puppetlabs':
  ensure => 'present',
  id     => '1054B7A24BD6EC30',
}

    You can additionally set the following attributes:

    • source: HTTP, HTTPS or FTP location of a GPG key or path to a file on the target host.
    • content: Instead of pointing to a file, pass the key in as a string.
    • server: The GPG key server to use. It defaults to keyserver.ubuntu.com.
    • keyserver_options: Additional options to pass to --keyserver.

    Because apt_key is a native type, you can use it and query for it with MCollective.

Defined Types

  • apt::builddep: Installs the build dependencies of a specified package.

    apt::builddep { 'glusterfs-server': }

  • apt::conf: Specifies a custom configuration file. The priority defaults to 50, but you can set the priority parameter to load the file earlier or later. The content parameter passes specified content, if any, into the file resource.

  • apt::hold: Holds a specific version of a package. You can hold a package to a full version or a partial version.

    To set a package's ensure attribute to 'latest' but get the version specified by apt::hold:

    apt::hold { 'vim':
  version => '2:7.3.547-7',
}

    Alternatively, if you want to hold your package at a partial version, you can use a wildcard. For example, you can hold Vim at version 7.3.*:

apt::hold { 'vim':
  version => '2:7.3.*',
}

  • apt::force: Forces a package to be installed from a specific release. This is particularly useful when using repositories that are unstable in Ubuntu, such as Debian.

    apt::force { 'glusterfs-server':
  release     => 'unstable',
  version     => '3.0.3',
  cfg_files   => 'unchanged',
  cfg_missing => true,
  require => Apt::Source['debian_unstable'],
}

    Valid values for cfg_files are:

    • 'new': Overwrites all existing configuration files with newer ones.
    • 'old': Forces usage of all old files.
    • 'unchanged: Updates only unchanged config files.
    • 'none': Provides backward-compatibility with existing Puppet manifests.

    Valid values for cfg_missing are 'true', 'false'. Setting this to 'false' provides backward compatability; setting it to 'true' checks for and installs missing configuration files for the selected package.

  • apt::key: Adds a key to the list of keys used by Apt to authenticate packages. This type uses the aforementioned apt_key native type. As such, it no longer requires the wget command on which the old implementation depended.

    apt::key { 'puppetlabs':
  key        => '1054B7A24BD6EC30',
  key_server => 'pgp.mit.edu',
}

apt::key { 'jenkins':
  key        => '9B7D32F2D50582E6',
  key_source => 'http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key',
}

  • apt::pin: Defined type that adds an Apt pin for a certain release.

    apt::pin { 'karmic': priority => 700 }
apt::pin { 'karmic-updates': priority => 700 }
apt::pin { 'karmic-security': priority => 700 }

    Note that you can also specify more complex pins using distribution properties.

    apt::pin { 'stable':
  priority        => -10,
  originator      => 'Debian',
  release_version => '3.0',
  component       => 'main',
  label           => 'Debian'
}

    If you want to pin a number of packages, you can specify the packages as a space-delimited string using the packages attribute, or you can pass in an array of package names.

  • apt::ppa: Adds a PPA repository using add-apt-repository. For example, apt::ppa { 'ppa:drizzle-developers/ppa': }.

  • apt::source: Adds an Apt source to /etc/apt/sources.list.d/. For example:

    apt::source { 'debian_unstable':
  comment           => 'This is the iWeb Debian unstable mirror',
  location          => 'http://debian.mirror.iweb.ca/debian/',
  release           => 'unstable',
  repos             => 'main contrib non-free',
  required_packages => 'debian-keyring debian-archive-keyring',
  key               => '8B48AD6246925553',
  key_server        => 'subkeys.pgp.net',
  pin               => '-10',
  include_src       => true,
  include_deb       => true
}

    For example, to configure your system so the source is the Puppet Labs Apt repository:

    apt::source { 'puppetlabs':
  location   => 'http://apt.puppetlabs.com',
  repos      => 'main',
  key        => '1054B7A24BD6EC30',
  key_server => 'pgp.mit.edu',
  }

Facts

The apt module includes a few facts to describe the state of the Apt system:

  • apt_updates: The number of updates available on the system
  • apt_security_updates: The number of updates which are security updates
  • apt_package_updates: The package names that are available for update. In Facter 2.0 and later, this will be a list type; in earlier versions, it is a comma-delimited string.
  • apt_update_last_success: The date, in epochtime, of the most recent successful apt-get update run. This is determined by reading the mtime of /var/lib/apt/periodic/update-success-stamp.

Note: The facts depend on 'update-notifier' being installed on your system. Though this is a GNOME daemon only the support files are needed so the package 'update-notifier-common' is enough to enable this functionality.

Hiera example

<pre>
apt::sources:
  'debian_unstable':
    location: 'http://debian.mirror.iweb.ca/debian/'
    release: 'unstable'
    repos: 'main contrib non-free'
    required_packages: 'debian-keyring debian-archive-keyring'
    key: '9AA38DCD55BE302B'
    key_server: 'subkeys.pgp.net'
    pin: '-10'
    include_src: 'true'
    include_deb: 'true'

  'puppetlabs':
    location: 'http://apt.puppetlabs.com'
    repos: 'main'
    key: '1054B7A24BD6EC30'
    key_server: 'pgp.mit.edu'
</pre>

Parameters

apt

  • always_apt_update: Set to 'true' to update Apt on every run. This setting is intended for development environments where package updates are frequent. Defaults to 'false'.
  • apt_update_frequency: Sets the run frequency for apt-get update. Defaults to 'reluctantly'. Accepts the following values:
    • 'always': Runs update at every Puppet run.
    • 'daily': Runs update daily; that is, apt-get update runs if the value of apt_update_last_success is less than current epoch time - 86400. If the exec resource apt_update is notified, apt-get update runs regardless of this value.
    • 'weekly': Runs update weekly; that is, apt-get update runs if the value of apt_update_last_success is less than current epoch time - 604800. If the exec resource apt_update is notified, apt-get update runs regardless of this value.
    • 'reluctantly': Only runs apt-get update if the exec resource apt_update is notified. This is the default setting.
  • disable_keys: Disables the requirement for all packages to be signed.
  • proxy_host: Configures a proxy host and stores the configuration in /etc/apt/apt.conf.d/01proxy.
  • proxy_port: Configures a proxy port and stores the configuration in /etc/apt/apt.conf.d/01proxy.
  • purge_sources_list: If set to 'true', Puppet purges all unmanaged entries from sources.list. Accepts 'true' or 'false'. Defaults to 'false'.
  • purge_sources_list_d: If set to 'true', Puppet purges all unmanaged entries from sources.list.d. Accepts 'true' or 'false'. Defaults to 'false'.
  • update_timeout: Overrides the exec timeout in seconds for apt-get update. Defaults to exec default (300).
  • update_tries: Sets how many times to attempt running apt-get update. Use this to work around transient DNS and HTTP errors. By default, the command runs only once.
  • sources: Passes a hash to create_resource to make new apt::source resources.
  • fancy_progress: Enables fancy progress bars for apt. Accepts 'true', 'false'. Defaults to 'false'.

####apt::unattended_upgrades

  • origins: The repositories from which to automatically upgrade included packages.
  • blacklist: A list of packages to not automatically upgrade.
  • update: How often, in days, to run apt-get update.
  • download: How often, in days, to run apt-get upgrade --download-only.
  • upgrade: How often, in days, to upgrade packages included in the origins list.
  • autoclean: How often, in days, to run apt-get autoclean.
  • randomsleep: How long, in seconds, to randomly wait before applying upgrades.

Testing

The apt module is mostly a collection of defined resource types, which provide reusable logic for managing Apt. It provides smoke tests for testing functionality on a target system, as well as spec tests for checking a compiled catalog against an expected set of resources.

Example Test

This test sets up a Puppet Labs Apt repository. Start by creating a new smoke test, called puppetlabs-apt.pp, in the apt module's test folder. In this test, declare a single resource representing the Puppet Labs Apt source and GPG key:

apt::source { 'puppetlabs':
  location   => 'http://apt.puppetlabs.com',
  repos      => 'main',
  key        => '1054B7A24BD6EC30',
  key_server => 'pgp.mit.edu',
}

This resource creates an Apt source named puppetlabs and gives Puppet information about the repository's location and the key used to sign its packages. Puppet leverages Facter to determine the appropriate release, but you can set this directly by adding the release type.

Check your smoke test for syntax errors:

$ puppet parser validate tests/puppetlabs-apt.pp

If you receive no output from that command, it means nothing is wrong. Then, apply the code:

$ puppet apply --verbose tests/puppetlabs-apt.pp
notice: /Stage[main]//Apt::Source[puppetlabs]/File[puppetlabs.list]/ensure: defined content as '{md5}3be1da4923fb910f1102a233b77e982e'
info: /Stage[main]//Apt::Source[puppetlabs]/File[puppetlabs.list]: Scheduling refresh of Exec[puppetlabs apt update]
notice: /Stage[main]//Apt::Source[puppetlabs]/Exec[puppetlabs apt update]: Triggered 'refresh' from 1 events>

The above example uses a smoke test to lay out a resource declaration and apply it on your system. In production, you might want to declare your Apt sources inside the classes where they’re needed.

Limitations

This module should work across all versions of Debian/Ubuntu and support all major Apt repository management features.

Development

Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can’t access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.

We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

You can read the complete module contribution guide on the Puppet Labs wiki.

License

The original code for this module comes from Evolving Web and was licensed under the MIT license. Code added since the fork of this module is licensed under the Apache 2.0 License like the rest of the Puppet Labs products.

The LICENSE contains both licenses.

Contributors

A lot of great people have contributed to this module. A somewhat current list follows: