Or, perhaps this is a case for an extlookup? I'm not fully familiar with that
function yet, but my inclination is that it might fit the bill.
Cheers,
Eric
On Wed, Jan 20, 2010 at 09:25:19AM +0800, Ohad Levy wrote:
> what about allowing the users to modify the tag lists?
> Ideally, you would nee
what about allowing the users to modify the tag lists?
Ideally, you would need a black list tag, which a script could read and feed
into puppetd command line arguments.
cheers,
Ohad
On Wed, Jan 20, 2010 at 4:14 AM, jb wrote:
> I'd like others to have the option to temporarily disable puppet fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why not use the 'noop' metaparam?
Instead of a notouch file, how about .file.noop which would simply set
noop => 'true' for that run perhaps with an extended message about using
a noop file.
Trevor
On 01/19/2010 04:37 PM, Nigel Kersten wrote:
> On T
On Tue, Jan 19, 2010 at 1:21 PM, Scott Smith wrote:
> Trevor Vaughan wrote:
>
>> Yes. But, in theory, this is a temporary measure.
>>
>> If it's not, then why are you managing that file in the first place?
>>
>>
> I monitor puppetd errors with splunk, so this could cause someone to get
> paged =(
Trevor Vaughan wrote:
Yes. But, in theory, this is a temporary measure.
If it's not, then why are you managing that file in the first place?
I monitor puppetd errors with splunk, so this could cause someone to get
paged =(
Good idea for those of us who don't, though :)
(If I see a feature
Yes. But, in theory, this is a temporary measure.
If it's not, then why are you managing that file in the first place?
Trevor
On Tue, Jan 19, 2010 at 3:54 PM, Scott Smith wrote:
> Trevor Vaughan wrote:
>>
>> As this would generally be a manual change, I would use 'chattr +i' on
>> Linux systems
Trevor Vaughan wrote:
As this would generally be a manual change, I would use 'chattr +i' on
Linux systems.
I haven't tried, but won't this cause the client to throw an error?
-scott
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post t
As this would generally be a manual change, I would use 'chattr +i' on
Linux systems.
Trevor
On Tue, Jan 19, 2010 at 3:14 PM, jb wrote:
> I'd like others to have the option to temporarily disable puppet from
> modify a file or directory...something along the lines of:
>
> ./something.conf.lock
>
2010/1/19 jb :
> I'd like others to have the option to temporarily disable puppet from
> modify a file or directory...something along the lines of:
>
> ./something.conf.lock
>
> causes
>
> ./something.conf
>
> to NOT be modified by puppet for as long the lock file exists
We discussed the concept o
I'd like others to have the option to temporarily disable puppet from
modify a file or directory...something along the lines of:
./something.conf.lock
causes
./something.conf
to NOT be modified by puppet for as long the lock file exists
it'd also be nice to be able to disable an entire directo
10 matches
Mail list logo
