9ad4fd682d
* 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
20 lines
450 B
Puppet
20 lines
450 B
Puppet
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,
|
|
}
|
|
}
|