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.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/zTjnubmS0mkJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
