Issue #5382 has been updated by Jacob Helwig.

I don't think I actually agree with `puppet` defaulting to `puppet apply` "by 
convention".  The convention we're moving to with all of the other commands is 
that they are sub-commands off of `puppet`, which has the convention that 
`puppet` itself is just a router to get you to the various sub-commands.  It 
seems like it would be confusing if we had the behaviour that `puppet` applied 
manifests, except when given a second argument that isn't a flag, or a file, 
where it will actually be a completely different command.

I'm definitely in favour of adding the deprecation warning to `puppet` without 
a subcommand.
----------------------------------------
Bug #5382: Legacy executables should issue deprecation warnings
https://projects.puppetlabs.com/issues/5382

Author: Nick Fagerlund
Status: Accepted
Priority: Normal
Assignee: 
Category: executables
Target version: 2.7.x
Affected Puppet version: 
Keywords: 
Branch: 


Since the single executable introduced in 2.6.0 is now the official way to 
invoke all of Puppet's functions, we should deprecate all the standalone 
executables (puppetmasterd, puppetd, puppet \[without a command\], puppetca, 
ralsh, puppetrun, puppetqd, filebucket, puppetdoc, and pi) and print warnings 
when they're used. I'm told it'd be impolite to start warning during 2.6, so 
let's start in 2.7.0.

In terms of documentation, I'm going to start describing these standalone 
executables as "legacy" and slated for deprecation; once 2.7 drops, I'll start 
describing them as deprecated and slated for removal. 


-- 
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.

Reply via email to