Title: Message Title
Josh Cooper commented on PUP-8566
Re: "puppet config print" should only emit diagnostic info when run with verbose or higher
Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/5d8590cca9d6000d05d0096e4250fe7f70ad5f82
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
Kris Bosland updated an issue
Puppet / PUP-8566
"puppet config print" should only emit diagnostic info when run with verbose or higher
Change By:
Kris Bosland
Release Notes Summary:
Extra information for puppet config print will now only be shown with verbose or debug options.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
Eric Sorenson commented on PUP-8566
Re: "puppet config print" should only emit diagnostic info when run with verbose or higher
Kris Bosland the subject header now accurately reflects acceptance criteria: '"puppet config print" should only emit diagnostic info when run with verbose or higher'
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
Josh Cooper commented on PUP-8566
Re: "puppet config print" should only emit diagnostic info when run with verbose or higher
The reason for multiple ways of doing the same thing is because originally there was only the --configprint option for agent and master. Then we started adding more applications, and made it possible for users to write their own applications. So rather than force everyone to re-implement the same logic, we have one puppet config application that can manage settings independent of any single run_mode. I agree --configprint is nice because you don't need to know which run_mode a particular application normally runs in, e.g. puppet lookup uses the master run_mode. But the "run_mode is terrible" boat left a long time ago. So I think it's better to make the section explicit rather than automagically resolving to the run_mode that the application will eventually switch to once its ruby code is loaded.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
Kris Bosland assigned an issue to Kris Bosland
Puppet / PUP-8566
"puppet config print" should only emit diagnostic info when run with verbose or higher
Change By:
Kris Bosland
Assignee:
Josh Cooper Kris Bosland
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
Kris Bosland commented on PUP-8566
Re: "puppet config print" should only emit diagnostic info when run with verbose or higher
Eric Sorenson, there is some back and forth on the desired solution - can you write an Acceptance Criteria? Thanks!
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
R.I.Pienaar commented on PUP-8566
Re: "puppet config print" should only emit diagnostic info when run with verbose or higher
Each command like master, agent, apply use different sections in the puppet.conf. Many other commands too and they can be quite confusing (which ones use user?) So never mind knowing this detail, puppet --configprint does the right thing and fetches it from the config file out of the appropriate section for that command. So the same CLI API to extracting the command appropriate information. I find this a lot nicer than puppet config print because you have to know a lot less to get at the information you want and have less scope for human error.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
James Ralston commented on PUP-8566
Re: "puppet config print" should only emit diagnostic info when run with verbose or higher
R.I.Pienaar wrote:
Master, apply etc all have --configprint and all does the right thing.
Ummm… ok, I'll ask it: why? Why have the exact same functionality duplicated across different command families? But back to the issue at hand: the original goal of PUP-2868 was to prevent novice users from running puppet config print without --section and then getting confused over which settings applied to which role. Issuing a big fat warning when --section is not used satisfies that goal. Therefore, I agree that the behavior of puppet config print should be reverted to only print the section if --verbose (or perhaps --debug) is passed. (I have no strong opinion as to whether the threshold is --verbose or --debug.) I originally suggested using --quiet to suppress printing the section, but I think this behavior change makes more sense than what I suggested, so I'm all for it.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit

Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8566
"puppet config print" should only emit diagnostic info when run with verbose or higher
Change By:
Josh Cooper
Sprint:
Platform Core Hopper KANBAN
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
Josh Cooper assigned an issue to Josh Cooper
Puppet / PUP-8566
"puppet config print" should only emit diagnostic info when run with verbose or higher
Change By:
Josh Cooper
Assignee:
Josh Cooper
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8566
"puppet config print" should only emit diagnostic info when run with verbose or higher
Change By:
Josh Cooper
Summary:
"puppet config print" needs --quiet option to disable new (default) verbosity should only emit diagnostic info when run with verbose or higher
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.