Jira (PUP-3638) Remove the manifest handling code from the util/rdoc parsers.
Title: Message Title Nicholas Fagerlund commented on PUP-3638 Re: Remove the manifest handling code from the util/rdoc parsers. Updates to the puppet doc application's help text / manpage were never completed, and its instructions remain misleading. - mode is no longer usable. -mode pdf has been busted since we stopped using RST for resource type docs. --outputdir is kaput. --all is wrong b/c it refers to removed features. --charset is kaput --modulepath is kaput --environment is kaput examples are partially whacked description is whacked Description doesn't refer to puppet strings, which I consider mandatory for removing the main function of puppet doc. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3272) Remove support for yaml on the network
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3272 Remove support for yaml on the network Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3272) Remove support for yaml on the network
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3272 Remove support for yaml on the network Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3280) Remove msi provider
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3280 Remove msi provider Change By: Nicholas Fagerlund Labels: docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3280) Remove msi provider
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3280 Remove msi provider Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2613) Change source_permissions default to :ignore
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2613 Change source_permissions default to :ignore Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2613) Change source_permissions default to :ignore
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2613 Change source_permissions default to :ignore Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2609) Don't allow source_permissions to be set to anything other than ignore on Windows
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2609 Don't allow source_permissions to be set to anything other than ignore on Windows Change By: Nicholas Fagerlund Labels: docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2609) Don't allow source_permissions to be set to anything other than ignore on Windows
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2609 Don't allow source_permissions to be set to anything other than ignore on Windows Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2559) Remove couchdb facts terminus and associated settings
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2559 Remove couchdb facts terminus and associated settings Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2559) Remove couchdb facts terminus and associated settings
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2559 Remove couchdb facts terminus and associated settings Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2558) Remove instrumentation system
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2558 Remove instrumentation system Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2558) Remove instrumentation system
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2558 Remove instrumentation system Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4007) Cannot disable use_srv_records via command line
Title: Message Title Nicholas Fagerlund commented on PUP-4007 Re: Cannot disable use_srv_records via command line Here's a fun question: where's that error message come from? I can't find it anywhere in the Puppet code. Well, anyway, I agree that putting the error message there is a great idea. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2702) Change environment_timeout default to unlimited
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2702 Change environment_timeout default to unlimited Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2647 Windows user provider reports that the password is created instead of changed Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2647 Windows user provider reports that the password is created instead of changed Change By: Nicholas Fagerlund Labels: docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3024) yumrepo: add setting deltarpm_percentage
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3024 yumrepo: add setting deltarpm_percentage Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3024) yumrepo: add setting deltarpm_percentage
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3024 yumrepo: add setting deltarpm_percentage Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2998) Allow log_level option to be specified in configuration file in addition to command line
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2998 Allow log_level option to be specified in configuration file in addition to command line Change By: Nicholas Fagerlund Labels: docs_reviewed redmine Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2998) Allow log_level option to be specified in configuration file in addition to command line
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2998 Allow log_level option to be specified in configuration file in addition to command line Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3331) Custom Types should be able to call all levels of auto* relationships.
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3331 Custom Types should be able to call all levels of auto* relationships. Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3331) Custom Types should be able to call all levels of auto* relationships.
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3331 Custom Types should be able to call all levels of auto* relationships. Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3336) Puppet is inconsistent about :libdir setting when multiple paths provided
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3336 Puppet is inconsistent about :libdir setting when multiple paths provided Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3336) Puppet is inconsistent about :libdir setting when multiple paths provided
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3336 Puppet is inconsistent about :libdir setting when multiple paths provided Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3429) Weekly tasks always notify 'trigger changed'
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3429 Weekly tasks always notify 'trigger changed' Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3429) Weekly tasks always notify 'trigger changed'
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3429 Weekly tasks always notify 'trigger changed' Change By: Nicholas Fagerlund Labels: customer docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3462) Hiera scope: add the key 'calling_class_path'
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3462 Hiera scope: add the key 'calling_class_path' Change By: Nicholas Fagerlund Labels: docs_reviewed hiera windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3462) Hiera scope: add the key 'calling_class_path'
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3462 Hiera scope: add the key 'calling_class_path' Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3719) Group resource non-authoritative by default
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3719 Group resource non-authoritative by default Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3719) Group resource non-authoritative by default
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3719 Group resource non-authoritative by default Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2628 Ability to add a member to a group, instead of specifying the complete list Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2628 Ability to add a member to a group, instead of specifying the complete list Change By: Nicholas Fagerlund Labels: docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3842) Ensure that Puppet 4 FOSS MSI includes MCO
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3842 Ensure that Puppet 4 FOSS MSI includes MCO Change By: Nicholas Fagerlund Labels: docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3842) Ensure that Puppet 4 FOSS MSI includes MCO
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3842 Ensure that Puppet 4 FOSS MSI includes MCO Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3844) Puppet MSI filename should be puppet-agent.msi by default
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3844 Puppet MSI filename should be puppet-agent.msi by default Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3844) Puppet MSI filename should be puppet-agent.msi by default
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3844 Puppet MSI filename should be puppet-agent.msi by default Change By: Nicholas Fagerlund Labels: docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3848) Puppet 4.0.0 should update Ruby to 2.1.5 and Facter to 2.4.0
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3848 Puppet 4.0.0 should update Ruby to 2.1.5 and Facter to 2.4.0 Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3848) Puppet 4.0.0 should update Ruby to 2.1.5 and Facter to 2.4.0
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3848 Puppet 4.0.0 should update Ruby to 2.1.5 and Facter to 2.4.0 Change By: Nicholas Fagerlund Labels: docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Nicholas Fagerlund commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client Rob Mattson Yes, the docs are misleading and that's what I filed a new ticket for. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Nicholas Fagerlund commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Fwiw, I think this revision passes the "explainability" smell test. (agent/* didn't, quite.) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Nicholas Fagerlund commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client Henrik Lindberg if you consider the bad error message the real bug here, could you either update the summary/description to say so, or close this as wontfix and open a new issue? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Nicholas Fagerlund commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client Created new issue DOC-1638 to fix that ambiguity, removing DOCS component from this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3626 cannot export file from puppet client via puppetdb to another puppet client Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3139) API docs don't mention POST API for catalogs
Title: Message Title Nicholas Fagerlund commented on PUP-3139 Re: API docs don't mention POST API for catalogs Hmm. so, the new and better API docs actually do mention POST for catalog: https://github.com/puppetlabs/puppet/blob/master/api/docs/http_catalog.md So this is kind of done. It's just that we also have old crappy api docs sitting around as well. At least, I think that's what Nigel's referring to. Part of my commitment for P4 is to get the real, continuously updated api docs posted on the site in a much better way. I'm inclined to just close this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2024) stdlib delete function modifies underlying array while implying it returns a modified copy
Title: Message Title Nicholas Fagerlund commented on PUP-2024 Re: stdlib delete function modifies underlying array while implying it returns a modified copy So, that behavior is horrible, right? And conflicts with the future parser's guarantee that values are immutable? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-304) Override does not propagate to hiera() function in interpolation tokens
Title: Message Title Nicholas Fagerlund updated an issue Hiera / HI-304 Override does not propagate to hiera() function in interpolation tokens Change By: Nicholas Fagerlund Summary: Override does not work with propagate to hiera() function in interpolation tokens Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-304) Override does not work with interpolation
Title: Message Title
Nicholas Fagerlund updated an issue
Hiera / HI-304
Override does not work with interpolation
Change By:
Nicholas Fagerlund
If you look up a piece of data that happens to use the hiera() function in an interpolation token— like: {code}value: '${hiera("other_lookup_key")}'{code}—and you provided a hierarchy override as an argument to the / original / lookup, Hiera will ignore the overridden hierarchy override when resolving the secondary lookup . According to Docs about lookup functions in interpolation tokens: https://docs.puppetlabs.com/hiera/1/variables.html# the documentation, - hiera accepts a -lookup-functionDocs about providing hierarchy override. It says overrides : https://docs.puppetlabs.com/hiera/1/puppet.html#hiera-lookup-functions {quote}Override (optional): the name of an arbitrary hierarchy level to insert at the top of the hierarchy. This lets you use a temporary modified hierarchy for a single lookup. (E.g., instead of a hierarchy of $clientcert -> $osfamily -> common, a lookup would use specialvalues -> $clientcert -> $osfamily -> common; you would need to be sure to have specialvalues.yaml or whatever in your Hiera data.){quote}This does not work with interpolation. When the variable is interpolated the original hierarchy is used. We have fixed this and will be submitting a patch but I wanted to make sure a bug was filed first. The bug goes back at least as far as Hiera 1.2.1.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to t
Jira (HI-304) Override does not work with interpolation
Title: Message Title
Nicholas Fagerlund updated an issue
Hiera / HI-304
Override does not work with interpolation
Change By:
Nicholas Fagerlund
If you look up a piece of data that happens to use the hiera() function in an interpolation token— like: {code}value: '${hiera("other_lookup_key")}'{code}—and you provided a hierarchy override as an argument to the /original/ lookup, Hiera will ignore the overridden hierarchy when resolving the lookup According to the documentation, hiera accepts a hierarchy override. It says:{quote}Override (optional): the name of an arbitrary hierarchy level to insert at the top of the hierarchy. This lets you use a temporary modified hierarchy for a single lookup. (E.g., instead of a hierarchy of $clientcert -> $osfamily -> common, a lookup would use specialvalues -> $clientcert -> $osfamily -> common; you would need to be sure to have specialvalues.yaml or whatever in your Hiera data.){quote}This does not work with interpolation. When the variable is interpolated the original hierarchy is used. We have fixed this and will be submitting a patch but I wanted to make sure a bug was filed first. The bug goes back at least as far as Hiera 1.2.1.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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.go
Jira (HI-298) Update FS layout for hiera
Title: Message Title Nicholas Fagerlund updated an issue Hiera / HI-298 Update FS layout for hiera Change By: Nicholas Fagerlund The coming update to the FS layout for our projects requires several changes to default pathing and config files to ensure that the correct directories are used. Off the top of my head this includes default datadir for hiera data.The new layout is described here:https://confluence.puppetlabs.com/display/DEL/Unified+Puppet+Agent+Layout Final decision is listed in this comment: https://tickets.puppetlabs.com/browse/HI-298?focusedCommentId=132439&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-132439 Summary:* Default config file on posix is /etc/puppetlabs/agent/code/hiera.yaml* Default datadir on posix is /etc/puppetlabs/agent/code/hieradata/* Defaults are same when used from Puppet, Ruby library, and cmd line. * Windows defaults do not change. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-304) Override does not work with interpolation
Title: Message Title Nicholas Fagerlund commented on HI-304 Re: Override does not work with interpolation This ticket needs a description of both the desired/expected behavior and the buggy behavior the PR is meant to fix. Stephen Gelman or Michael Smith or Thomas Hallgren, could one of you please edit the description to add that? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3963) Error message gives wrong advice for allowed module names
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-3963 Error message gives wrong advice for allowed module names Issue Type: Bug Assignee: Unassigned Created: 2015/02/04 4:56 PM Priority: Normal Reporter: Nicholas Fagerlund Under some conditions, Puppet will issue an error message like Error: Invalid module name .gitignore; module names must be alphanumeric (plus '-'), not '.gitignore'. That's wrong! You should definitely never have hyphens in your module names, but underscores are encouraged. The docs do not list hyphens as valid characters in module and class names, and we've publicly stated for years that it's a bug that it works and we'll make it stop working at our earliest convenience. Here's the relevant code: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/module.rb#L343 Add Comment
Jira (PUP-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Nicholas Fagerlund commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match My main thrust is: let's also make sure it's impossible for non-regex node names to conflict with class names (remembering that something like web is a valid short node name that will match nodes like web.example.com). If that concern's addressed, I'm all good. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-14) Allow access to structured data
Title: Message Title
Nicholas Fagerlund updated an issue
Hiera / HI-14
Allow access to structured data
Change By:
Nicholas Fagerlund
Ever since puppet has supported data structures, hiera has not been able to access those structures. With work in PP-542, facts themselves, which are the most commonly used values in hiera, are becoming data structures, and so this issue is becoming a large problem.There are several ways we can approach this: 1. Implement another "function" to access facts: {noformat} myvar: %{fact(osfamily)} {noformat} 2. Implement parsing of structure access: {noformat} myvar: %{facts[osfamily]} {noformat} 3. Implement structure traversal (a more obviously limited form of structure access): {noformat} myvar: %{facts.osfamily} {noformat}I propose that in order to keep hiera simple the most correct form might be option 3. Part of this work is to decide on which one is best for hiera and then implement it. **Pre-docs:** Added in https://github.com/puppetlabs/pre-docs/pull/34.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 (FACT-96) Deprecate 'facter --puppet'
Title: Message Title Nicholas Fagerlund commented on FACT-96 Re: Deprecate 'facter --puppet' Kylo Ginsberg Ah cool. I agree that's okay. So the target is 3.0 for a removal, and... either 2.x for a deprecation, or a docs-only deprecation? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-96) Deprecate 'facter --puppet'
Title: Message Title Nicholas Fagerlund commented on FACT-96 Re: Deprecate 'facter --puppet' Oh man, puppet facts find. I'd like to start a discussion here: if we're going to push users from something relatively easy and constrained to something else, I believe the something else shouldn't be an indirector face, because they're whatever the opposite is of easy, constrained, and fit-for-particular-purpose. I really hate those auto-generated find/destroy/etc. interfaces, and do not get me started on --terminus. Let's decide what the use cases are for getting facts via Puppet's CLI, intentionally design a nice bare-bones interface for doing those things, and replace the current puppet facts. If we can. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3838) puppet console output for warning is red, which is unnecessarily alarming
Title: Message Title Nicholas Fagerlund commented on PUP-3838 Re: puppet console output for warning is red, which is unnecessarily alarming �� Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Nicholas Fagerlund commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match Henrik Lindberg Eric Sorenson Hmm, so it looks like this fix expects that non-regexp node definitions will never have a name that conflicts with the name of a class, right? Given the behavior around truncated hostnames (https://docs.puppetlabs.com/puppet/3.7/reference/lang_node_definitions.html#matching), I believe we can't rely on that. We should probably apply a (different) prefix to literal node names, as well. Obligatory reminder that we have no reliable abstract way to refer to node scope, so it's effectively anonymous. Obligatory reminder of that problem where Puppet can sometimes reduce disjoint regexes to identical node names if their special characters are removed, although I might be the only one who's mortally offended by that. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Nicholas Fagerlund assigned an issue to Kylo Ginsberg Puppet / PUP-2564 Specify UTF-8 as a default encoding for puppet Change By: Nicholas Fagerlund Assignee: Nicholas Fagerlund Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Nicholas Fagerlund commented on PUP-2564 Re: Specify UTF-8 as a default encoding for puppet I agree. Also, I consider the docs component done. In this file (https://docs.puppetlabs.com/puppet/latest/reference/lang_summary.html#files) we already said manifests should use UTF8; I'll change that to a stronger "must" and call it a day. I think we should resolve this ticket and open new tickets for implementation issues. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1119) Upon 3.0 release, edit config_file_puppetdb.markdown in puppet-docs repo
Title: Message Title Nicholas Fagerlund commented on PDB-1119 Re: Upon 3.0 release, edit config_file_puppetdb.markdown in puppet-docs repo Sorry for making this a PDB ticket, we just need a timed reminder that will move whenever the release date moves. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1119) Upon 3.0 release, edit config_file_puppetdb.markdown in puppet-docs repo
Title: Message Title Nicholas Fagerlund created an issue PuppetDB / PDB-1119 Upon 3.0 release, edit config_file_puppetdb.markdown in puppet-docs repo Issue Type: Task Affects Versions: PDB 3.0.0 Assignee: Unassigned Components: DOCS Created: 2015/01/14 5:57 PM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Nicholas Fagerlund We used to maintain docs about the puppetdb.conf file in the Puppet reference manual, at e.g. https://docs.puppetlabs.com/puppet/3.7/reference/config_file_puppetdb.html. Ryan Senior moved the canonical version of this documentation into the puppetdb repo, and PuppetDB 3.0 will be the first version to release with that file present in the docs. Right now, we're linking to that file using "master" as the URL segment, because master is excluded from the "latest" alias. Once there's a numbered version with that file present, we should change "master" to "latest" anywhere that file is linked in the Puppet docs proper.
Jira (PUP-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Nicholas Fagerlund commented on PUP-3656 Re: Prefetch eats all exceptions, there is no way to fail out. Kylo Ginsberg Rad, thanks. I added some stuff to be more obvious about this being a breaking change, since that ends up being important for release notes. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-3656
Prefetch eats all exceptions, there is no way to fail out.
Change By:
Nicholas Fagerlund
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/transaction.rb#L306-L310This bug still exists in the master branch as of today and was introduced in 2.7.8 with this commit:https://github.com/puppetlabs/puppet/commit/000a2d811c740f4179a0cd4ced38e886858cf01fThe rescue condition means that any exception raised by providers during prefetch gets logged but then swallowed by Puppet. As a result of this, any provider which relies *only* on prefetch to find all instances will end up running the resource creation regardless of whether the resource exists or not.In order to negate this behaviour, provider authors would need to create checks for instance existence which run during the creation phase as well, which defeats the point of having prefetch in the first place.---Note to docs: module authors who use the {{prefetch}} method may want to be aware of the changes in this fix. Two things to consider:# previously, the prefetch method could throw *any* exception and puppet would carry on. As discussed above this is the wrong behavior in general, however some module authors may have stumbled across this, allowed/encouraged prefetch to throw exceptions, and let puppet runs succeed. So modules should be examined for this assumption.# the only two legitimate causes for prefetch to throw an exception now are {{LoadError}} and (added in this puppet 4.0) {{Puppet::MissingCommand}} This is a breaking change in 4.0.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3656 Prefetch eats all exceptions, there is no way to fail out. Change By: Nicholas Fagerlund Component/s: Breaking Change Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3656 Prefetch eats all exceptions, there is no way to fail out. Change By: Nicholas Fagerlund Labels: breaking Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-400) Manage hidden windows packages
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-400
Manage hidden windows packages
I'm copying over the description from the redmine export, since it has context this ticket was missing.
Change By:
Nicholas Fagerlund
Currently, the windows package provider excludes hidden applications (those whose SystemComponent registry value is set to 1) from its {{instances}} method (both exe and msi). This is done so that puppet has parity with what is displayed in Add/Remove Programs, e.g. {{SQL Server 2008 R2 SP2 Common Files}} .But it means if you install a hidden application, then puppet won't know it's installed, and try to reinstall it next time. For example, https://groups.google.com/d/topic/puppet-users/ftvvO51bX1U/discussion
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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 ht
Jira (PUP-3272) Remove support for yaml on the network
Title: Message Title Nicholas Fagerlund commented on PUP-3272 Re: Remove support for yaml on the network The config reference will automatically pick up the removed setting. Other than that, we're fine; no other docs besides the 3.3 release notes refer to this setting. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3577) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Nicholas Fagerlund commented on PUP-3577 Re: Is the Jira tidy-up done for this release and prepared for the next one? Henrik Lindberg These filter links don't work if I'm not logged in as you. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3578) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on PUP-3578 Re: Prepare long form release notes and short form release story Release notes are ready to push once the go/no meeting is finished. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3578) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on PUP-3578 Re: Prepare long form release notes and short form release story Here's a blurb: Puppet 3.7.3 is a bug fix release in the Puppet 3.7 series. It gives Windows users the useful new `$system32` fact (due to packages now pulling in Facter 2.3), and fixes some bugs with directory environments, the `PATH` variable on Windows, and the future parser. It also lays groundwork for some future Puppet Server improvements. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 (FACT-743) Docs pushed
Title: Message Title Nicholas Fagerlund commented on an issue Re: Docs pushed This is ready once we go/nogo it. Add Comment Facter / FACT-743 Docs pushed Push the documentation updates to docs.puppetlabs.com. Dependencies: * Go / No Go meeting (Status - Ship it!) 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-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Nicholas Fagerlund commented on an issue Re: Puppet needs to use default keylength 2048 on FIPS enabled systems In that case I think I agree with Trevor's approach. Add Comment Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems FIPS 140-2 does not allow for the use of 4096 bit keys. Therefore, the initial certificate generation of a key using a key length > 2048 bits will fail. Any system that is FIPS enabled, should use a 2048 bit key when generating the initial CA and server certificates. 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 (FACT-694) ec2 fact doesn't work for openstack with kvm as it is restricted for xen
Title: Message Title Nicholas Fagerlund commented on an issue Re: ec2 fact doesn't work for openstack with kvm as it is restricted for xen Excellent, thank you for the summary! Add Comment Facter / FACT-694 ec2 fact doesn't work for openstack with kvm as it is restricted for xen Since the code in ec2 facter restrict only for xen, this doesnt work with openstack with kvm hypervisor. 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 (FACT-694) ec2 fact doesn't work for openstack with kvm as it is restricted for xen
Title: Message Title Nicholas Fagerlund commented on an issue Re: ec2 fact doesn't work for openstack with kvm as it is restricted for xen Hey Kylo Ginsberg, can you give a bit more context for the release notes? Would people expect Amazon EC2 facts to work on Openstack? Why? Who was affected by this bug? Add Comment Facter / FACT-694 ec2 fact doesn't work for openstack with kvm as it is restricted for xen Since the code in ec2 facter restrict only for xen, this doesnt work with openstack with kvm hypervisor. 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-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Nicholas Fagerlund commented on an issue Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Does OpenSSL at least crash with an informative message? Can we do anything after OpenSSL crashes and tell the user what might be up? Can we detect what's up before OpenSSL crashes and give a message then? Anyway, my answer about addressing this in docs stands: we can put something on the website and say we technically did something, but we can't put something on the website and say it solves the problem. Users won't know to even check the docs unless they get a clear signal about what just happened to them. Add Comment Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems FIPS 140-2 does not allow for the use of 4096 bit keys. Therefore, the initial certificate generation of a key using a key length > 2048 bits will fail. Any system that is FIPS enabled, should use a 2048 bit key when generating the initial CA and server certificates. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribe
Jira (PUP-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Nicholas Fagerlund commented on an issue Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Kylo Ginsberg The only sufficient docs for this would be just-in-time docs. (Explanation in keylength setting: no one will go looking there. Explanation in install guide: clogs up guide with irrelevant info and degrades experience for all non-FIPS users. Explanation in "troubleshooting" page where info goes to die: no one will go looking there. Explanation in separate "FIPS" page: no one will go looking there.) Anyway, when we fail to generate initial certificates due to FIPS being enabled, we should, AT THAT TIME, emit a message explaining what happened and pointing at the keylength setting. What is the current symptom of this failure? We should change that symptom to be explicit and helpful. That's the solution I'd be satisfied with. Add Comment Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems FIPS 140-2 does not allow for the use of 4096 bit keys. Therefore, the initial certificate generation of a key using a key length > 2048 bits will fail. Any system that is FIPS enabled, should use a 2048 bit key when generating the initial CA and server certificates. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3130) Remove "hidden" $_timestamp fact
Title: Message Title Nicholas Fagerlund commented on an issue Re: Remove "hidden" $_timestamp fact Col. Okay, I've filed DOC-1320 to track deprecated features for 4.0. Add Comment Puppet / PUP-3130 Remove "hidden" $_timestamp fact 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-3130) Remove "hidden" $_timestamp fact
Title: Message Title Nicholas Fagerlund commented on an issue Re: Remove "hidden" $_timestamp fact Ha, interesting. So this is a method that will be deprecated in 4.x and removed in 5.0? I think that's the first of those, isn't it? Add Comment Puppet / PUP-3130 Remove "hidden" $_timestamp fact 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-3415) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on an issue Re: Prepare long form release notes and short form release story http://docspreview2.puppetlabs.lan/puppet/3.7/reference/release_notes.html And the preview, if you have VPN. Add Comment Puppet / PUP-3415 Prepare long form release notes and short form release story Collaborating with product for release story Dependencies: * Is there a JIRA ticket targeted at the release for every commit? * Is there a commit for every JIRA ticket targeted at the release? 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-3415) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on an issue Re: Prepare long form release notes and short form release story https://github.com/puppetlabs/puppet-docs/blob/pup372/source/puppet/3.7/reference/release_notes.markdown In a branch and ready to go. Add Comment Puppet / PUP-3415 Prepare long form release notes and short form release story Collaborating with product for release story Dependencies: * Is there a JIRA ticket targeted at the release for every commit? * Is there a commit for every JIRA ticket targeted at the release? 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-3294) Remove support for :parent
Title: Message Title Nicholas Fagerlund commented on an issue Re: Remove support for :parent Kylo Ginsberg Gotcha, thanks for the ping. Removed it. Add Comment Puppet / PUP-3294 Remove support for :parent lib/puppet/metatype/manager.rb:88: Puppet.deprecation_warning "option :parent is deprecated. It has no effect" 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection Change By: Nicholas Fagerlund Assignee: Josh Cooper 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Nicholas Fagerlund commented on an issue Re: puppet reports "end of file reached" if server closes HTTP connection Okay, I think https://github.com/puppetlabs/puppet-docs/commit/7992414d722959fbb46054ee6f51980d86de30bc should resolve this bug. Josh Cooper, see anything I missed? Add Comment Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection I have two dirname.rb functions in my code, one from stdlib and one in a different module I installed at an earlier stage. This has never been a problem, puppet has somehow chosen one of them and not complained about it. After upgrading to 3.7.0 on the clients, the puppetruns crashes with "Error: Could not retrieve catalog from remote server: end of file... 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-bu
Jira (PUP-3150) config_version setting in environment.conf uses relative pathing
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: config_version setting in environment.conf uses relative pathing
Docs updated, will build in about 15m.
Add Comment
Puppet / PUP-3150
config_version setting in environment.conf uses relative pathing
If directory environments are configured, and you create an environment.conf in an environment, and you set the config_version parameter using a command that doesn't include the full path to the binary in question, such as: {noformat} config_version = 'git --git-dir $confdir/environments/$environment/.git rev-parse HEAD' {noformat} Puppet will att...
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-3150) config_version setting in environment.conf uses relative pathing
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: config_version setting in environment.conf uses relative pathing
Oh, lol, I hadn't thought about that interfering with the way we otherwise default to finding binaries in the PATH. Oh well, you should be using absolute paths to binaries anyway, who even knows what's in puppet's PATH in the first place. Yeah, I'll update the docs.
Add Comment
Puppet / PUP-3150
config_version setting in environment.conf uses relative pathing
If directory environments are configured, and you create an environment.conf in an environment, and you set the config_version parameter using a command that doesn't include the full path to the binary in question, such as: {noformat} config_version = 'git --git-dir $confdir/environments/$environment/.git rev-parse HEAD' {noformat} Puppet will att...
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
Jira (PUP-3212) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on an issue Re: Prepare long form release notes and short form release story Short form story can be as follows: Puppet 3.7.1 is a bug fix release in the Puppet 3.7 series. It fixes regressions introduced by Puppet 3.7.0, some issues with directory environments, and a few other bugs. Add Comment Puppet / PUP-3212 Prepare long form release notes and short form release story Collaborating with product for release story Dependencies: * Is there a JIRA ticket targeted at the release for every commit? * Is there a commit for every JIRA ticket targeted at the release? 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-bug
Jira (PUP-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Nicholas Fagerlund commented on an issue Re: In Puppet Gemfile, allow env var to indicate Puppet is already on load path Christopher Price Is this change relevant to end-users or community developers, or only relevant to developers at the company? Like, what's the situation where you'd want to set PUPPET_LOADED? Add Comment Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path We have a use case where the puppet source code is already available on the ruby load path before we run bundler, and need a way to conditionally exclude the `gem` line that references puppet. After some discussion, it sounds like an environment variable is the preferred way of doing this. 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 h
Jira (PUP-3240) Remove ignoreimport setting
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-3240 Remove ignoreimport setting Issue Type: Bug Assignee: Unassigned Created: 12/Sep/14 2:36 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Nicholas Fagerlund The `import` keyword is deprecated and slated for removal in 4.0. We should kill the ignoreimport setting while we're at it. As far as deprecating it goes, I figure it can be a docs-only deprecation. I'll add it to the list of deprecated 3.x features. Add Comment
Jira (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Nicholas Fagerlund commented on an issue Re: puppet reports "end of file reached" if server closes HTTP connection The only other places I think this could be mentioned are the release notes (with an UPGRADE WARNING flag) and the rack puppet master reference page (https://docs.puppetlabs.com/puppet/latest/reference/services_master_rack.html). Add Comment Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection I have two dirname.rb functions in my code, one from stdlib and one in a different module I installed at an earlier stage. This has never been a problem, puppet has somehow chosen one of them and not complained about it. After upgrading to 3.7.0 on the clients, the puppetruns crashes with "Error: Could not retrieve catalog from remote server: end of file... 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.c
Jira (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Nicholas Fagerlund commented on an issue Re: puppet reports "end of file reached" if server closes HTTP connection Looks like that directive can be set at virtual host scope: http://httpd.apache.org/docs/2.2/mod/core.html#keepalivetimeout Should we recommend setting that in the Passenger guide and/or the example vhost that ships with puppet? https://docs.puppetlabs.com/guides/passenger.html Add Comment Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection I have two dirname.rb functions in my code, one from stdlib and one in a different module I installed at an earlier stage. This has never been a problem, puppet has somehow chosen one of them and not complained about it. After upgrading to 3.7.0 on the clients, the puppetruns crashes with "Error: Could not retrieve catalog from remote server: end of file... 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+
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Nicholas Fagerlund commented on an issue Re: Block $environment in directory based environment configuration settings And we're gonna disallow $environment in the manifest and modulepath settings in environment.conf, right? That seems sensible, since the whole point of DIRECTORY environments is that having everything more or less in one place removes a layer of hard-to-reason-about indirection. I could see people doing something wild like two directories per environment, which seems like a bad idea. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... 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 g
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Nicholas Fagerlund commented on an issue Re: Block $environment in directory based environment configuration settings config_version is the only legit one I can think of. I read back through the list of important settings and nothing else seemed relevant. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... 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, vi
Jira (PUP-3160) uid 500 is not purged
Title: Message Title Nicholas Fagerlund commented on an issue Re: uid 500 is not purged Kylo Ginsberg Yes! This will require a change to text in the Puppet repo, for the `resources` resource type. Does this also affect behavior under OpenBSD? Is its ceiling of 1000 also exclusive rather than inclusive? Add Comment Puppet / PUP-3160 uid 500 is not purged The docs for unless_system_user specify "This keeps system users from being purged. By default, it does not purge users whose UIDs are less than or equal to 500, but you can specify a different UID as the inclusive limit." which is the observed behavior, but it not correct. System users are < 500, not <= 500. The patch to fix this is trivial, but fi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You
Jira (PUP-3104) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on an issue Re: Prepare long form release notes and short form release story The short form story can be: Puppet 3.7.0 is a backward-compatible features and fixes release in the Puppet 3 series. The biggest things in this release are: A nearly-final implementation of the Puppet 4 language Preview support for a new, fast, natively compiled Facter 64-bit Puppet packages for Windows Lots of deprecations to prepare for Puppet 4.0 Windows users: make sure you read the release notes, since the question of which package to install isn't necessarily obvious. (Depending on how your testing shakes out, you may need to continue using the 32-bit package for a while.) Add Comment Puppet / PUP-3104 Prepare long form release notes and short form release story Collaborating with product for release story Dependencies: * Is there a JIRA ticket targeted at the release for every commit? * Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Kurt Wall I'm not the one to ask! I was trying to find that out myself. But yes, that's what I understand from Adrien's response.
Add Comment
Puppet / PUP-1527
After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
gtAfter upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources, data taken from hiera. When hiera has the following data: "check_apt_security" : { "check_command" : "check_nrpe_1arg!check_apt_security", "contact_groups" : "sladmins", "normal_check_interval" : 10, ...
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 g
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Nicholas Fagerlund commented on an issue Re: Use a manifest setting in [master] as global manifests Docs weighing in, sorry it took me a minute to get to this. Joshua Partlow, for the effect you're describing here, the name "default_manifest" works fine. (It sounds like we're still wrangling over the effect, though.) Option 1 in James' comment above sounds fiendishly difficult to document and comprehend. I can go into why if it isn't clear. Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file resour... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3122) It's time we wrote a more usable no cert found warning!
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: It's time we wrote a more usable no cert found warning!
I'm waffling on the idea of telling the user WHERE to sign.
In an old-school deep-fried one-master setup, yeah, sign it on the master.
In modern PE, maybe you'd rather sign it in the console.
With the JVM master, the CA service is a separate component, which is on a specific server that may or may not be also acting as a puppet master.
so
Add Comment
Puppet / PUP-3122
It's time we wrote a more usable no cert found warning!
When you run the agent after it's submitted a CSR, but before the master has signed it, you get the warning {{no certificate found and waitforcert is disabled}}. This causes an incredible amount of consternation in the field because it sounds like "you done screwed up". Can we simply amend it to something like this? {{No certificate found and waitfo...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
