Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title
Nick Walker commented on an issue
Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
I agree that puppet config print should not work without specifying a section because it does not output enough information to let us know what section or runmode it ran it and confuses users.
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
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2038 `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4 Kylo Ginsberg, Andy Parker: Any thoughts about adding the print subface to the depreciation list for 3.6 or will we ultimately be able to let faces switch run modes? Change By: Charlie Sharpsteen Assignee: KyloGinsberg Labels: faces Add Comment 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.
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title
Andy Parker commented on an issue
Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Zachary Stern, can you provide some examples (or point to bugs) of puppet config print being wrong?
As for runmode, that is a concept that is slowly going away. You can specify what part of the configuration you want to see with puppet config print --section .
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,
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title Andy Parker assigned an issue to Zachary Stern Puppet / PUP-2038 `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4 Change By: Andy Parker Assignee: KyloGinsberg ZacharyStern Add Comment 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.
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
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 }}.
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.
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title Andy Parker commented on an issue Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4 Zachary Stern, you might want to read the docs. Help for puppet config print be puppet help config print USAGE: puppet config print [--section SECTION_NAME] (all | setting [setting ...] Prints the value of a single setting or a list of settings. OPTIONS: --render-as FORMAT - The rendering format to use. --verbose - Whether to log verbosely. --debug- Whether to log debug information. --section SECTION_NAME - The section of the configuration file to interact with. See 'puppet man config' or 'man puppet-config' for full help. I understand that the terminology changed a little WRT this. Before there were always runmodes and we never talked about the config file as something to be interpreted. The puppet config print command needs to work across many different views of the config file, and the runmode system was impossible for us to control accurately and so --section was added. What your output is showing you is that you asked for two settings: master and certname. Master is of course not a setting and so has no value. Maybe it should issue an error in that case? Certname is a real setting and so it gives you a value. By default this will be the value from the main section of the puppet configs. Add Comment Puppet / PUP-2038 `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title
Kylo Ginsberg commented on an issue
Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Zachary Stern the output is strange because of the bare -
in your snippet: replace it with
-setting.
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
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title Zachary Stern created an issue Puppet / PUP-2038 `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4 Issue Type: Bug Assignee: Unassigned Created: 25/Mar/14 4:50 PM Priority: Normal Reporter: Zachary Stern 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. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title
Zachary Stern commented on an issue
Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Or alternatively, come up with a way to specify runmode with config print, and keep it, to maintain consistency with the newly implemented puppet config set, and deprecate --configprint.
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
