module-apt/manifests/key.pp

define apt::key ($source, $ensure = 'present') {
  validate_re(
    $name, '\.gpg$',
    'An apt::key resource name must have the .gpg extension',
  )

  file {
    "/etc/apt/trusted.gpg.d/${name}":
      ensure => $ensure,
      source => $source,
      notify => Exec['apt_updated'],
  }
}
Linting. 2015-08-31 11:54:28 +02:00			`define apt::key ($source, $ensure = 'present') {`
Add validation for apt::key's name. It's great to document requirements in README, but error'ing out whenever the user messes up is even better IMO. 2015-08-31 12:00:09 +02:00			`validate_re(`
			`$name, '\.gpg$',`
			`'An apt::key resource name must have the .gpg extension',`
			`)`

add apt::key resource to deploy arbitrary keys 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-11 16:07:47 +02:00			`file {`
Linting. 2015-08-31 11:54:28 +02:00			`"/etc/apt/trusted.gpg.d/${name}":`
allow for binary keys that can be removed 2015-06-11 16:21:56 +02:00			`ensure => $ensure,`
Linting. 2015-08-31 11:54:28 +02:00			`source => $source,`
[refactor] Unify `apt-get update` into one resource 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-26 14:42:17 +01:00			`notify => Exec['apt_updated'],`
add apt::key resource to deploy arbitrary keys 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-11 16:07:47 +02:00			`}`
			`}`