We unfortunately have some modifications to core Puppet providers that are not
upstream. We are working on pull requesting our changes, but we would like to
upgrade to a modern Puppet version in parallel. I was able to monkey patch
Puppet 4.5 without issue by placing the patches in a module, but wh
Hello,
Looks like the concat module may do the job?
$my_template = '/my/config.file'
concat { $my_template:
}
concat::fragment { 'standard contents':
target => $my_template,
content => template('my.epp'),
}
And then in the Amavis profile class:
concat::fragment { 'extra spec
Christopher Wood wrote:
> Top post, I'm not skilled enough to read this hence not sure where I'd
> interject. You may be better off using simpler constructs so that
> people with a wider variety of skill levels in your organization can
> contribute.
>
> What problems are you encountering where de
Top post, I'm not skilled enough to read this hence not sure where I'd
interject. You may be better off using simpler constructs so that
people with a wider variety of skill levels in your organization can
contribute.
What problems are you encountering where describing state is not
sufficient to c
Hi,
I hope I can descripe the challenge.
/etc/puppetlabs/code/environments/production/manifests/nodes.pp:
node default {
include common
}
/etc/puppetlabs/code/modules/common/manifests/init.pp:
class common inherits config {
include $classes
[...]
/etc/puppetlabs/code/modules/config/manifest
