You can create arrays of identical resources:
file { [ '/etc/motd',
'/etc/issue',
'/etc/issue.net',
]:
ensure => file,
owner=> 0,
group=> 0,
content => template('manage_banners/some_banner_text.erb'),
}
Under the hood, when the catalog is compiled, it
Its probably easiest to explain what I want to accomplish.
I want to create the following 3 files: */etc/motd, /etc/issue,
/etc/issue.net* from a single (1) puppet file resource using the content =>
template('template.erb') syntax.
I don't want to create 3 separate file resources and use the
On Fri, Sep 16, 2016 at 06:44:36PM +0100, R.I.Pienaar wrote:
>
>
> - Original Message -
> > From: "Christopher Wood"
> > To: "puppet-users"
> > Sent: Friday, 16 September, 2016 19:39:21
> > Subject: Re: [Puppet Users] notify
- Original Message -
> From: "Christopher Wood"
> To: "puppet-users"
> Sent: Friday, 16 September, 2016 19:39:21
> Subject: Re: [Puppet Users] notify resource different between 3 and 4?
> On Fri, Sep 16, 2016 at 06:17:48PM
On Fri, Sep 16, 2016 at 06:17:48PM +0100, R.I.Pienaar wrote:
>
>
> - Original Message -
> > From: "Christopher Wood"
> > To: "puppet-users"
> > Sent: Friday, 16 September, 2016 19:10:23
> > Subject: [Puppet Users] notify
- Original Message -
> From: "Christopher Wood"
> To: "puppet-users"
> Sent: Friday, 16 September, 2016 19:10:23
> Subject: [Puppet Users] notify resource different between 3 and 4?
> While trying to figure out the reduce
While trying to figure out the reduce function with notice/notify I happened
across this thing. It looks like an unquoted array in the notify resource's
message only appears as its first array item. Not sure if it's a bug.
I couldn't find any documentation to say if this was intended and I
PuppetConf is coming up in just about a month, in San Diego, CA. It would
be wonderful to see you there. If you haven't been to one before, it's a
great time to learn about all things automations and DevOps. The talk
line-up this year looks stellar, and the hallways will be packed with
people
Hi,
The roles and profiles to setup puppetdb masterless and agent configs.
This way one can test eg exported resources without setting up the full puppet
server stack.
https://github.com/witjoh/vagrant_puppetdb_apply
I hope someone can make use of this
--
Johan De Wit
Open Source
Thanks.
While I see that Ansible is a nice tool, the clientless access requiring a
login has a fatal flaw when compared to puppet.
More than once we have had a PAM, SSHD or similar setup get corrupted over
dozens, if not all, systems. We were able to fix in Puppet and get the
corrections pushed
Am Donnerstag, 15. September 2016 14:53:57 UTC+2 schrieb HPUX_PUPPET:
>
> ...
>
> This post was mainly about seeing if Puppet / Factor had been tweaked over
> the years to pull lists of installed RPMs given Red Hat Satellite 6 using
> Puppet as part of their software management and server
11 matches
Mail list logo