Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Jorie Tappa commented on PUP-2868
Re: `puppet config print` confusing for users
Manually verified output of warnings if no section is declared, and updated text in the help for config. Tested out {{config print }}with different options, all looks good.
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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-2868 `puppet config print` confusing for users Change By: Jorie Tappa Assignee: Jorie Tappa 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Melissa Stone updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Melissa Stone QA Risk Assessment: Manual 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Melissa Stone commented on PUP-2868 Re: `puppet config print` confusing for users This has passed CI with puppet-agent 5.4.0.507.gf67d266 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Assignee: 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland commented on PUP-2868 Re: `puppet config print` confusing for users Release notes added. 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kris Bosland Release Notes Summary: puppet config print, set, and delete now print the environment and section on stderr to reduce user confusion. puppet config print also warns the user if they do not specify a section. 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Eric Delaney commented on PUP-2868 Re: `puppet config print` confusing for users Kris Bosland Can you add release notes if needed? 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper commented on PUP-2868 Re: `puppet config print` confusing for users Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/ad5541b1742279efb38af12d6e063d1110720660 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes assigned an issue to Kris Bosland Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Assignee: 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Melissa Stone assigned an issue to Unassigned Puppet / PUP-2868 `puppet config print` confusing for users Change By: Melissa Stone Assignee: Melissa Stone 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper assigned an issue to Melissa Stone Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Assignee: Kris Bosland Melissa Stone 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland commented on PUP-2868 Re: `puppet config print` confusing for users Updated acceptance criteria to include info for config set and config delete. Please let me know if you have a comment. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kris Bosland Acceptance Criteria: * rspec tests includes ability to ensure that output is being written to stderr* test to validate warning to stderr when no section provided* config help - manually verify content* stdout is not altered * add the message for section and environment to config set and config delete Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kris Bosland Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.4.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper commented on PUP-2868 Re: `puppet config print` confusing for users Commit 82b2f1189f1cd6b11814a1d468569438039028b9 causes puppet to default the section to :main (symbol), which never matches "main", so it creates a duplicate section each time. If you later use inifile to manage the file, it gets confused by duplicate sections. $ cat setconfig.sh #!/bin/sh cat < ~/.puppetlabs/etc/puppet/puppet.conf # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html [main] certname = r1nc1m63jxi6u3e.delivery.puppetlabs.net
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Past Haus commented on PUP-2868 Re: `puppet config print` confusing for users We're seeing some surprising behavior in PE possibly related to this changeset. I guess the first odd thing is that if a setting doesn't exist anywhere (and a [main] section exists), a new [main] section is added at the bottom of puppet.conf. This happens with each invocation, so after calling puppet config set 3 times, there are 4 [main] sections in puppet.conf. Starting with a puppet.conf that looks like the following: # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html [main] certname = r1nc1m63jxi6u3e.delivery.puppetlabs.net server = r1nc1m63jxi6u3e.delivery.puppetlabs.net user = pe-puppet group = pe-puppet
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Melissa Stone commented on PUP-2868 Re: `puppet config print` confusing for users Manually verified with 5.3.3.679.g26b954e [root@yx32o85umtg6j0r ~]# puppet config print server Warning: No section specified; defaulting to 'main'. Set the config section by using the `--section` flag. For example, `puppet config --section user print foo`. For more information, see https://puppet.com/docs/puppet/latest/configuration.html Resolving settings from section 'main' in environment 'production' foo [root@yx32o85umtg6j0r ~]# yum info puppet-agent Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Installed Packages Name: puppet-agent Arch: x86_64
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-2868 `puppet config print` confusing for users Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-2868 `puppet config print` confusing for users Change By: Eric Delaney Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper commented on PUP-2868 Re: `puppet config print` confusing for users Merged to master in https://github.com/puppetlabs/puppet/commit/e9bf54fd34387fc6bd9ddc81f97cc9d270e2aa8b Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kris Bosland Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kris Bosland Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Jacob Helwig updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Jacob Helwig
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. 'main' is the default.An example: You may have a server setting that is already in the agent setting. When you ran puppet config set server "value" - that will throw it in the "main" section. There already exists a server setting in the "agent" section that is overriding this. The next time you run puppet config print - you will get the one out of the main section (not the overriding agent setting)1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.comAlso print any other settings found that may/will override this setting as in the example above - "Setting is also defined in the following sections: X, Y, Z"2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section (should probably work with [~garrett.guillotte] on this) :* what the list of commonly used sections are * guidance on naming sections* the output of the help command point to the sections documentation* Include a good solid example of sections (what settings go in what section)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Acceptance Criteria: * rspec tests includes ability to ensure that output is being written to stderr* test to validate warning to stderr when no section provided* config help - manually verify content * stdout is not altered Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Craig Gomes
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. 'main' is the default.An example: You may have a server setting that is already in the agent setting. When you ran puppet config set server "value" - that will throw it in the "main" section. There already exists a server setting in the " agent " section that is overriding this. The next time you run puppet config print - you will get the one out of the main section (not the overriding agent setting)1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.comAlso print any other settings found that may/will override this setting as in the example above - "Setting is also defined in the following sections: X, Y, Z"2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section:* what the list of commonly used sections are * guidance on naming sections* the output of the help command point to the sections documentation* Include a good solid example of sections (what settings go in what section)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Craig Gomes
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. 'main' is the default. An example: You may have a server setting that is already in the agent setting. When you ran puppet config set server "value" - that will throw it in the "main" section. There already exists a server setting in the agent section that is overriding this. The next time you run puppet config print - you will get the one out of the main section (not the overriding agent setting) 1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.com Also print any other settings found that may/will override this setting as in the example above - "Setting is also defined in the following sections: X, Y, Z" 2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section:* what the list of commonly used sections are * guidance on naming sections* the output of the help command point to the sections documentation* Include a good solid example of sections (what settings go in what section)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Acceptance Criteria: * rspec tests includes ability to ensure that output is being written to stderr* test to validate warning to stderr when no section provided * config help - manually verify content Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Craig Gomes
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section.1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.com2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section , and :* what the list of commonly used sections are along with * guidance on naming sections . * the output of the help command point to the sections documentation* Include a good solid example of sections (what settings go in what section)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Craig Gomes
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section.1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.com2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section, and what the list of valid commonly used sections are along with guidance on naming sections .
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Acceptance Criteria: Acceptance * rspec tests includes ability to ensure that output is being written to stderr * test to validate warning to stderr when no section provided Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Acceptance Criteria: Acceptance tests includes ability to ensure that output is being written to stderr Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Josh Cooper
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. 1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.com2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section, and what the list of valid sections are.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Eric Sorenson commented on PUP-2868 Re: `puppet config print` confusing for users Got pinged on this by Josh Cooper - I like the idea of always emitting (to STDERR, so programmatic use will continue to work) a message about which section it's operating on. If no - section is specified, it should say " -section flag omitted, defaulting to 'user' settings - settings won't affect 'agent' execution" (or something similar). The puppetserver setting situation is a different problem. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Assignee: Andrew Parker Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Moses Mendoza Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Russell Mull updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Russell Mull Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Russell Mull updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Russell Mull Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Nick Walker commented on PUP-2868 Re: `puppet config print` confusing for users I think this ticket is still valid. Users are still wasting time running puppet config print and being confused when the settings don't match what they expect. The issue is even worse since the ticket was reported as a number of settings still exist in puppet.conf for configuring master settings but aren't honored by puppet server. IMO puppet config print is more likely to confuse users than it is to help them. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kurt Wall commented on PUP-2868 Re: `puppet config print` confusing for users This ticket has not been updated in some time and is now being closed due to inactivity. This isn't necessarily a statement that this ticket isn't important - other issues may have demanded precedence since it was filed, or it may have simply slipped through the cracks. If any viewer/watcher feels closing this ticket is an error, please re-open it and add a comment explaining. Our apologies in advance for any mistake on this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Zachary Stern updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Zachary Stern Assignee: ZacharyStern AndyParker 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-2868) `puppet config print` confusing for users
Title: Message Title
Zachary Stern commented on an issue
Re: `puppet config print` confusing for users
+1 to what Nick said.
People run puppet config print server and expect to get the value of server they've set in [main] or [agent], and get back puppet. They then start wondering why their configuration in puppet.conf isn't taking effect, when in fact it is, and they're simply using puppet config print wrong.
Add Comment
Puppet / PUP-2868
`puppet config print` confusing for users
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command. The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request...
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
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Andy Parker created an issue Puppet / PUP-2868 `puppet config print` confusing for users Issue Type: Bug Affects Versions: 3.4.0 Assignee: Unassigned Created: 30/Jun/14 2:07 PM Priority: Normal Reporter: Andy Parker puppet config print doesn't require a --section to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command. The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. Add Comment
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Andy Parker assigned an issue to Zachary Stern Zachary Stern, Nick Walker, could you two provide a bit of a run down about how users have been confused? What commands are they executing and what output do they expect to see? If you have suggestions to have it better match their expectations and have it clearer to them when it isn't, that would be really helpful as well. Puppet / PUP-2868 `puppet config print` confusing for users Change By: Andy Parker Assignee: 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-2868) `puppet config print` confusing for users
Title: Message Title
Nick Walker commented on an issue
Re: `puppet config print` confusing for users
Andy Parker to my knowledge the largest problem is someone runs puppet config print setting_name and they expect it to be either the agent or the master setting but it's really the user run mode which is less used.
I think in order to resolve that confusion we could do one or both of the following:
1. Output which section or run mode the command ran in 2. Force the user to choose a run mode or section so there's no question about which it ran in
Add Comment
Puppet / PUP-2868
`puppet config print` confusing for users
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command. The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you
