Issue #5365 has been updated by Nigel Kersten. Status changed from Needs design decision to Investigating
The problem is that --test is badly named. I believe it's meant to indicate "test a client which normally runs as a daemon". I really don't think we can change the semantics of "-t/--test" right now. It's far too embedded in the community consciousness. ---------------------------------------- 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.
