Issue #5365 has been updated by Rudy Gevaert.
I see your point. However I'm sure many people find it counter intuitive... Changing it will not really break things. Also people will be running it interactively so they will see that the behavior changed. ---------------------------------------- Refactor #5365: --test command line option is confusing https://projects.puppetlabs.com/issues/5365 Author: Rudy Gevaert Status: Investigating Priority: Normal Assignee: Nigel Kersten Category: executables Target version: Affected Puppet version: Branch: Hi, test: Enable the most common options used for testing. These are +onetime+, +verbose+, +ignorecache, +no-daemonize+, and +no-usecacheonfailure+. noop: Use +noop+ mode where the daemon runs in a no-op or dry-run mode. This is useful for seeing what changes Puppet will make without actually executing the changes. I think that --test should also include --noop. I have difficulty explaining to people when they want to test a puppet run it will actually change the system. Also it easier to remember and more natural to type in: puppet agent --test to see what the run will do. Now you need to type in puppet agent --test --noop -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
