Issue #5365 has been updated by Nigel Kersten.
It's not good enough to tell people they need to supply all the arguments that used to make up "test" if they want to keep the same functionality after we add "noop" to the list of arguments. We also have a reasonable number of users who run "noop" in daemon mode to get regular reports on their simulated runs and thus want "noop" without everything else that "test" implies. You want to have "noop" be part of "test". We can't make you all happy :) ---------------------------------------- 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.
