This has been extremely useful in my environment when importing the odd
'unique snowflake' type server quickly without having to make any code/logic
changes or introduce large numbers of ENC values to disable certain
functionality or alter the flow of your puppet code.
Yes. Puppet doesn't
On 20.08.2012, at 23:08, Sean Carolan wrote:
It's not really the cleanest-looking thing, but the easiest option for
your particular case is to wrap the file resource in an if statement
like this:
if (! $::security_limits_disabled) {
file { '/etc/security/limits.conf':
...
}
It's not really the cleanest-looking thing, but the easiest option for
your particular case is to wrap the file resource in an if statement
like this:
if (! $::security_limits_disabled) {
file { '/etc/security/limits.conf':
...
}
}
Super, thanks Martin!
--
You received this
It's not really the cleanest-looking thing, but the easiest option for
your particular case is to wrap the file resource in an if statement
like this:
if (! $::security_limits_disabled) {
file { '/etc/security/limits.conf':
...
}
}
Thanks, this is just what I was looking
On Fri, 2012-08-17 at 15:41 -0700, Sean Carolan wrote:
You don't say what version of puppet you're using, whether you're using
an ENC, or whether you're already using either extlookup() or hiera(),
so it's really difficult to suggest something that integrates well with
your current
In regard to: [Puppet Users] Override a file{} directive - is it possible?,...:
Maybe one of you can help with this. I have a class that's got a
file{} type directive in it. It populates /etc/security/limits.conf
with specific settings. I have a small handful of hosts where we want
to manage
You don't say what version of puppet you're using, whether you're using
an ENC, or whether you're already using either extlookup() or hiera(),
so it's really difficult to suggest something that integrates well with
your current environment.
Sorry I didn't provide more detail. We're using
