Issue #2276 has been updated by James Turnbull.
Whilst it's not hugely backwards-compatible I'd just use "puppet". You can migrate/deprecate existing funtionality for "puppet". ---------------------------------------- Feature #2276: Most Puppet functionality should be available via a single command http://projects.reductivelabs.com/issues/2276 Author: Luke Kanies Status: Accepted Priority: Normal Assigned to: community - Category: executables Target version: 0.26.0 Complexity: Unknown Affected version: 0.24.8 Keywords: Similar to the recent consolidation in 'git', the new Application class enables us to provide a single application that has access to all of the executable functionality. E.g., I could see the following commands: <pre> puppetcmd ral user foo ensure=absent puppetcmd ca --sign foo.madstop.com puppetcmd server start puppetcmd client start puppetcmd bucket restore /my/file puppetcmd doc --reference type puppetcmd run --host foo </pre> I'm definitely not recommending the name be 'puppetcmd', but this basic idea could simplify things a good bit. The thing I really like about it, though, is that it will force us to make all of the applications much more consistent - they'll each register exactly the commands they support, and the Application class can handle querying and listing those commands for this new executable. -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
