module-puppetlabs-apt/manifests/conf.pp

define apt::conf (
  $content       = undef,
  $ensure        = present,
  $priority      = 50,
  $notify_update = undef,
) {

  unless $ensure == 'absent' {
    unless $content {
      fail('Need to pass in content parameter')
    }
  }

  apt::setting { "conf-${name}":
    ensure        => $ensure,
    priority      => $priority,
    content       => template('apt/_conf_header.erb', 'apt/conf.erb'),
    notify_update => $notify_update,
  }
}
Adds apt::{conf,backports} and variable style. With the addition of this patch two new defines will be added; one to manage APT configuration files (apt::conf) and one that abstracts out the requirements needed to turn on backport repositories (apt::backports). In addition, the patch takes the opportunity to clean up variable definitions so they follow a consistent pattern of setting local variables to the fully qualified value stored in the apt::params class. Previously all variable used within a class directly addressed the apt::params namespace when ever the variable was used. In the pattern they now adhere to we can more easily switch the namespace data lives in or externalize it even more using hiera. 2012-04-11 23:54:13 +02:00			`define apt::conf (`
MODULES-2269: Expose notify_update setting * Expose the underlying notify_update setting of the apt::settings resource This is because not all configuration file changes should trigger an apt::update notification * apt::pin also shouldn't result in an apt-update call Adding a pin configuration should apply to the next apt-get update call it shouldn't trigger one itself. * Added documentation * Add tests for apt::conf notify_update 2015-07-23 18:15:53 +02:00			`$content = undef,`
			`$ensure = present,`
apt::setting expects priority to be an integer, set defaults accordingly Signed-off-by: Mathias Merscher <Mathias.Merscher@dg-i.net> 2016-04-19 12:28:45 +02:00			`$priority = 50,`
MODULES-2269: Expose notify_update setting * Expose the underlying notify_update setting of the apt::settings resource This is because not all configuration file changes should trigger an apt::update notification * apt::pin also shouldn't result in an apt-update call Adding a pin configuration should apply to the next apt-get update call it shouldn't trigger one itself. * Added documentation * Add tests for apt::conf notify_update 2015-07-23 18:15:53 +02:00			`$notify_update = undef,`
Cleanup apt-module puppet-lint related issues. 2012-05-03 18:51:14 +02:00			`) {`
apt::conf: Don't require content `ensure=>absent`. 2015-04-14 12:41:57 +02:00
			`unless $ensure == 'absent' {`
			`unless $content {`
			`fail('Need to pass in content parameter')`
			`}`
			`}`

Convert to use apt::setting instead of file resources This adds consistency across the module 2015-02-24 23:57:31 +01:00			`apt::setting { "conf-${name}":`
MODULES-2269: Expose notify_update setting * Expose the underlying notify_update setting of the apt::settings resource This is because not all configuration file changes should trigger an apt::update notification * apt::pin also shouldn't result in an apt-update call Adding a pin configuration should apply to the next apt-get update call it shouldn't trigger one itself. * Added documentation * Add tests for apt::conf notify_update 2015-07-23 18:15:53 +02:00			`ensure => $ensure,`
			`priority => $priority,`
			`content => template('apt/_conf_header.erb', 'apt/conf.erb'),`
			`notify_update => $notify_update,`
Adds apt::{conf,backports} and variable style. With the addition of this patch two new defines will be added; one to manage APT configuration files (apt::conf) and one that abstracts out the requirements needed to turn on backport repositories (apt::backports). In addition, the patch takes the opportunity to clean up variable definitions so they follow a consistent pattern of setting local variables to the fully qualified value stored in the apt::params class. Previously all variable used within a class directly addressed the apt::params namespace when ever the variable was used. In the pattern they now adhere to we can more easily switch the namespace data lives in or externalize it even more using hiera. 2012-04-11 23:54:13 +02:00			`}`
			`}`