Problem with the 'noop' metaparameter and using the --noop flag

[Galed Friedmann]

Hey,

I've stumbled across a weird thing, wanted to know if it is intentional or maybe a bug..

When using the 'noop' metaparemeter inside a manifest, for example:

file{ "/tmp/test":

ensure => file,

noop => true,

}

Running this in a normal puppet run will run this in noop like it should. When trying to run 'puppet agent --noop', the --noop flag actually reverses the 'noop' metaparameter in the manifest and that resource will actually run, which is kind of dangerous in a production environment, while testing a manifest and assuming noop resources will not be running..

Has this happened to anybody?

Galed.

[Stefan Schulte]

I tried to reproduce it with puppet apply but failed. What version are
you running and do you have noop = true or noop = false in you
puppet.conf?

-Stefan