Merge pull request #372 from jbondpdx/revised-readme
DOC-249: Revised and updated apt readme
This commit is contained in:
Daniele Sluijters
commit
6619ad843f
1 changed files with 270 additions and 239 deletions
315
README.md
315
README.md
|
|
@ -1,51 +1,39 @@
|
|||
apt
|
||||
===
|
||||
# apt
|
||||
|
||||
[](https://travis-ci.org/puppetlabs/puppetlabs-apt)
|
||||
|
||||
Overview
|
||||
--------
|
||||
## Overview
|
||||
|
||||
The apt module provides a simple interface for managing APT source, key, and definitions with Puppet.
|
||||
The apt module provides a simple interface for managing Apt source, key, and definitions with Puppet.
|
||||
|
||||
Module Description
|
||||
------------------
|
||||
## 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 **strongly** recommend that you **do not use short keys**, as they pose a serious security issue by opening you up to collision attacks.
|
||||
**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
|
||||
-----
|
||||
## Setup
|
||||
|
||||
**What apt affects:**
|
||||
### What apt affects:
|
||||
|
||||
* package/service/configuration files for APT
|
||||
* NOTE: Setting the `purge_preferences` or `purge_preferences_d` parameters to 'true' will destroy any existing configuration that was not declared with Puppet. The default for these parameters is 'false'.
|
||||
* your system's `sources.list` file and `sources.list.d` directory
|
||||
* NOTE: Setting the `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'.
|
||||
* system repositories
|
||||
* authentication keys
|
||||
* 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.
|
||||
To begin using the apt module with default parameters, declare the class with `include apt`.
|
||||
|
||||
include apt
|
||||
Any Puppet code that uses anything from the apt module requires that the core apt class be declared.
|
||||
|
||||
Puppet code that uses anything from the apt module requires that the core apt class be declared.
|
||||
## Usage
|
||||
|
||||
Usage
|
||||
-----
|
||||
|
||||
Using the apt module consists predominantly of declaring classes that provide the desired functionality and features.
|
||||
|
||||
### apt
|
||||
|
||||
`apt` provides a number of common resources and options that are shared by the various defined types in this module, so you **must always** include this class in your manifests.
|
||||
|
||||
The parameters for `apt` are not generally required and are predominantly for development environment use cases.
|
||||
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,
|
||||
|
|
@ -58,22 +46,99 @@ The parameters for `apt` are not generally required and are predominantly for de
|
|||
update_timeout => undef,
|
||||
fancy_progress => undef
|
||||
}
|
||||
```
|
||||
|
||||
Puppet will manage your system's `sources.list` file and `sources.list.d` directory but will do its best to respect existing content.
|
||||
## 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::builddep
|
||||
* `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.
|
||||
|
||||
Installs the build depends of a specified package.
|
||||
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.
|
||||
|
||||
apt::builddep { 'glusterfs-server': }
|
||||
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::force
|
||||
* `apt::params`: Sets defaults for the apt module parameters.
|
||||
|
||||
Forces a package to be installed from a specific release. This class is particularly useful when using repositories, like Debian, that are unstable in Ubuntu.
|
||||
The cfg_files parameter controls wether newer or older configuration files should be used or only unchanged configuration files should be updated. Cfg_missing forces the provider to install all missing configuration files. Both are optional.
|
||||
* `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',
|
||||
|
|
@ -81,36 +146,19 @@ The cfg_files parameter controls wether newer or older configuration files shoul
|
|||
cfg_missing => true,
|
||||
require => Apt::Source['debian_unstable'],
|
||||
}
|
||||
```
|
||||
|
||||
You can additionally set the following attributes:
|
||||
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.
|
||||
|
||||
* `cfg_files`: "new", "old", "unchanged" or "none" (default). "new" will overwrite all existing configuration files with newer ones, "old" will force usage of all old files and "unchanged" only updates unchanged config files whereas setting "none" will don't do anything but providing backward-compatability with existing puppet manifests.
|
||||
* `cfg_missing`: "true" or "false". Setting cfg_missing to false will provide backward compatability whereas setting true will add an aptitude/apt-get parameter which checks and installs missing configuration files for the selected package.
|
||||
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
|
||||
|
||||
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, it can be used in and queried for with MCollective.
|
||||
|
||||
### 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`: 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',
|
||||
|
|
@ -120,17 +168,19 @@ the `wget` command on which the old implementation depended.
|
|||
key => '9B7D32F2D50582E6',
|
||||
key_source => 'http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key',
|
||||
}
|
||||
```
|
||||
|
||||
### apt::pin
|
||||
|
||||
Adds an apt pin for a certain release.
|
||||
* `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 you can also specifying more complex pins using distribution properties.
|
||||
Note that you can also specify more complex pins using distribution properties.
|
||||
|
||||
```
|
||||
apt::pin { 'stable':
|
||||
priority => -10,
|
||||
originator => 'Debian',
|
||||
|
|
@ -138,56 +188,15 @@ Note you can also specifying more complex pins using distribution properties.
|
|||
component => 'main',
|
||||
label => 'Debian'
|
||||
}
|
||||
```
|
||||
|
||||
If you wish to pin a number of packages you may specify the packages as a space
|
||||
delimited string using the `packages` attribute or pass in an array of package
|
||||
names.
|
||||
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::hold
|
||||
* `apt::ppa`: Adds a PPA repository using `add-apt-repository`. For example, `apt::ppa { 'ppa:drizzle-developers/ppa': }`.
|
||||
|
||||
When you wish to hold a package in Puppet, it should be done by passing in
|
||||
'held' as the ensure attribute to the package resource. However, a lot of
|
||||
public modules do not take this into account and generally do not work well
|
||||
with an ensure of 'held'.
|
||||
|
||||
Moreover, when Puppet is told to hold a package, it holds it at the current version installed; there is no way to tell it to both install a specific version **and** hold that version, unless you use an exec resource that wraps `dpkg --set-selections` or `apt-mark`.
|
||||
|
||||
At first glance, it seems this issue could also be solved by passing the version required to the ensure attribute---but that only means that Puppet will install that
|
||||
version after it processes the package. It does not inform apt that we want
|
||||
this package to be held; that is, should another package want to upgrade this one (because of a version requirement in a dependency, for example), we want apt to refuse.
|
||||
|
||||
To solve this issue, use apt::hold. Implement this by creating a preferences file with a priority of 1001. Under normal circumstances, this preference will always win. Because the priority is > 1000, apt will maintain the required version, downgrading the current package if necessary.
|
||||
|
||||
With this, you can now 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 Vim at version 7.3.*, you can pass in a version with a glob:
|
||||
|
||||
apt::hold { 'vim':
|
||||
version => '2:7.3.*',
|
||||
}
|
||||
|
||||
### apt::ppa
|
||||
|
||||
Adds a ppa repository using `add-apt-repository`.
|
||||
|
||||
apt::ppa { 'ppa:drizzle-developers/ppa': }
|
||||
|
||||
### apt::release
|
||||
|
||||
Sets the default apt release. This class is particularly useful when using repositories, like Debian, that are unstable in Ubuntu.
|
||||
|
||||
class { 'apt::release':
|
||||
release_id => 'precise',
|
||||
}
|
||||
|
||||
### apt::source
|
||||
|
||||
Adds an apt source to `/etc/apt/sources.list.d/`.
|
||||
* `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/',
|
||||
|
|
@ -200,32 +209,31 @@ Adds an apt source to `/etc/apt/sources.list.d/`.
|
|||
include_src => true,
|
||||
include_deb => true
|
||||
}
|
||||
```
|
||||
|
||||
If you would like to configure your system so the source is the Puppet Labs APT repository:
|
||||
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',
|
||||
}
|
||||
|
||||
### 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---this should happen when config files get updated or other relevant changes occur. If you set the `always_apt_update` parameter, the update will run on every Puppet run.
|
||||
```
|
||||
|
||||
### Facts
|
||||
|
||||
There are a few facts included in the apt module describing the state of the apt system:
|
||||
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 that `apt-get update` last ran successfully. This is determined by reading the mtime of the file `/var/lib/apt/periodic/update-success-stamp`. That file is generated by the `/etc/apt/apt.conf.d/15update-stamp` file.
|
||||
* `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.
|
||||
|
||||
#### Hiera example
|
||||
|
||||
```
|
||||
<pre>
|
||||
apt::sources:
|
||||
'debian_unstable':
|
||||
|
|
@ -245,52 +253,75 @@ apt::sources:
|
|||
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`.
|
||||
|
||||
### Testing
|
||||
|
||||
The apt module is mostly a collection of defined resource types, which provide reusable logic that can be leveraged to manage 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.
|
||||
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 will set 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:
|
||||
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.
|
||||
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
|
||||
`$ 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.
|
||||
|
||||
Implementation
|
||||
--------------
|
||||
|
||||
### apt::backports
|
||||
|
||||
Adds the necessary components to get backports for Ubuntu and Debian. The release name defaults to `$lsbdistcodename`. Setting this manually can cause undefined behavior (read: universe exploding).
|
||||
|
||||
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 the newest version wins/becomes the candidate apt will want to install or upgrade to. This means that if a package is available from Backports it and its dependencies will be pulled in from Backports unless you explicitly set the `ensure` attribute of the `package` resource to `installed`/`present` or a specific version.
|
||||
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.
|
||||
This module should work across all versions of Debian/Ubuntu and support all major Apt repository management features.
|
||||
|
||||
Development
|
||||
------------
|
||||
|
|
|
|||
Loading…
Reference in a new issue