Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4

[Zachary Stern (JIRA)]

Title: Message Title

Zachary Stern commented on an issue   Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4 Andy Parker it's not so much "wrong" as that it always shows settings from the User runmode, rather than master or agent, and that's generally not what customers are looking to find. This ends mostly just confusing people. As to specifying a specific block of configuration, I'm confused by your example {{ puppet config print --section XXXX }}. lolcalhost :: ~ % puppet config print -- master certname master = certname = lolcalhost.wifi.puppetlabs.net lolcalhost :: ~ % puppet config print master certname master = certname = lolcalhost.wifi.puppetlabs.net I consider the above output to be "strange"? What's "master = " In addition, customers generally are not looking for a command to "tell them what's in the file". They are looking for a command that shows them the resolved value of that setting, for that runmdode. Add Comment   Puppet / PUP-2038 `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4 {{puppet config print}} is rarely accurate, and mostly just confusing to users. It should be deprecated in favor of {{puppet agent --configprint <someoption>}}, which currently works fairly well. Puppet 3.something should issue deprecation warnings, and Puppet 4 should remove it entirely. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.