Jira (PUP-2209) FreeBSD Service definition not working with missing rc.conf definition
Title: Message Title Kurt Wall assigned an issue to Dolf Schimmel Puppet / PUP-2209 FreeBSD Service definition not working with missing rc.conf definition Change By: Kurt Wall Assignee: Kurt Wall Dolf Schimmel Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2209) FreeBSD Service definition not working with missing rc.conf definition
Title: Message Title Kurt Wall commented on PUP-2209 Re: FreeBSD Service definition not working with missing rc.conf definition Hi. Is this still an issue for you? I’ve put this ticket’s status into “Needs Information” and assigned it to you. Please either (a) update it with the information I’ve requested and re-assign it to me if you need more help, or (b) change the status to “Closed” if you were able to resolve the issue on your own or it is no longer an issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2175) Consider Adding Provider To The Default Output of `puppet resource package`
Title: Message Title Kurt Wall commented on PUP-2175 Re: Consider Adding Provider To The Default Output of `puppet resource package` Seems like a Product Management decision. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2209) FreeBSD Service definition not working with missing rc.conf definition
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2209 FreeBSD Service definition not working with missing rc.conf definition Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2175) Consider Adding Provider To The Default Output of `puppet resource package`
Title: Message Title Kurt Wall assigned an issue to Eric Sorenson Puppet / PUP-2175 Consider Adding Provider To The Default Output of `puppet resource package` Change By: Kurt Wall Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1443) Add `capabilities` to the puppet agent / master communication.
Title: Message Title Kurt Wall assigned an issue to Eric Sorenson Puppet / PUP-1443 Add `capabilities` to the puppet agent / master communication. Change By: Kurt Wall Assignee: Not Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1443) Add `capabilities` to the puppet agent / master communication.
Title: Message Title Kurt Wall commented on PUP-1443 Re: Add `capabilities` to the puppet agent / master communication. Definitely a feature request on which Product Mgmt should rule. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1443) Add `capabilities` to the puppet agent / master communication.
Title: Message Title Kurt Wall assigned an issue to Not Eric Sorenson Puppet / PUP-1443 Add `capabilities` to the puppet agent / master communication. Change By: Kurt Wall Assignee: Not Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7393) AIX Provider acts strange with user resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7393 AIX Provider acts strange with user resource Change By: Josh Cooper When a user is in a group on a Linux server and a user resource is created for that user, if new groups are specified in the resource, the user is moved out of his previous groups into the groups specified. In AIX the user stays in his old groups and gets added to his new groups. The AIX functionality should mimic the Linux functionality. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6564) Support Ruby 2.3.x with Puppet 4.5.2
Title: Message Title Josh Cooper commented on PUP-6564 Re: Support Ruby 2.3.x with Puppet 4.5.2 Thank you for reporting this. This issue has already been addressed in a later release of Puppet. If you experience this issue against the current version of Puppet, please add a comment to this ticket with your reproduction scenario. For more info on getting the current version of Puppet Agent, see https://docs.puppet.com/puppet/latest/install_pre.html. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6660) cached catalogs setting not respected when --test is specified
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6660 cached catalogs setting not respected when --test is specified Change By: Josh Cooper Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1593) facter 2.4.6 should disable proxy when fetching metadata from 169.254.169.254
Title: Message Title Robert August Vincent II created an issue Facter / FACT-1593 facter 2.4.6 should disable proxy when fetching metadata from 169.254.169.254 Issue Type: Bug Assignee: Unassigned Components: Community, PE Created: 2017/03/23 8:11 PM Priority: Normal Reporter: Robert August Vincent II Facter version 2.4.6 uses the openuri mixin, which is affected by the ENV['http_proxy'] setting. It retrieves EC2 metadata by contacting the metadata server at 169.254.169.254. If http_proxy is set, facter will wind up retrieving the metadata of the proxy server rather than its own metadata. To avoid this, calls to open must include the ", :proxy => nil" modifier. In fact, some of the metadata calls have this modifier, but not all. I have submitted PR 1532 to resolve this problem. Add Comment
Jira (PUP-7391) Fix problem with "Attempt to redefine entity" when using type aliases as class parameter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7391 Fix problem with "Attempt to redefine entity" when using type aliases as class parameter Change By: Henrik Lindberg Release Notes Summary: An error with "Attempt to redefine entity" could occur in some cases when a type alias was resolved. This occurred if a module's init.pp would also reference and resolve the same type and if that init.pp needed to be loaded to resolve the type in the first place. This problem is now fixed. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7391) Fix problem with "Attempt to redefine entity" when using type aliases as class parameter
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7391 Fix problem with "Attempt to redefine entity" when using type aliases as class parameter Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7391) Fix problem with "Attempt to redefine entity" when using type aliases as class parameter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7391 Fix problem with "Attempt to redefine entity" when using type aliases as class parameter Change By: Henrik Lindberg Fix Version/s: PUP 4.10.z Fix Version/s: PUP 4.10.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7364) Parser result no longer contains current method
Title: Message Title Thomas Hallgren commented on PUP-7364 Re: Parser result no longer contains current method Henrik Lindberg, the fix I did was to retain the current alias for the model method. That doesn't help in this case since parse_string was changed to return the actual AST instead of the Factory that created it. Puppet Strings isn't affected by that. The proposed solution seems OK to me, perhaps with an added deprecation message that informs the user that the extra call to current is no longer needed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4885) Master and Agent should not share libdir
Title: Message Title Ruth Linehan assigned an issue to Unassigned Puppet / PUP-4885 Master and Agent should not share libdir Change By: Ruth Linehan Assignee: Ruth Linehan Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4885) Master and Agent should not share libdir
Title: Message Title Ruth Linehan assigned an issue to Ruth Linehan Puppet / PUP-4885 Master and Agent should not share libdir Change By: Ruth Linehan Assignee: Ruth Linehan Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1377) Allow different database configurations per environment
Title: Message Title Eric Sorenson commented on PUP-1377 Re: Allow different database configurations per environment I'm closing this as a duplicate of an older issue that more accurately reflects the problem: PUP-1078. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7360) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7360 Apparently a Puppet Hiera error message points to a 404 Change By: Henrik Lindberg Release Notes Summary: Hiera deprecation messages contained a URL to our documentation site that produced a 404 (not found). The reason being that the URL contains the ".z" version of puppet, and it should only contain "x.y" part of version. This is now fixed. Sprint: PDE 2017-04-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7360) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Henrik Lindberg commented on PUP-7360 Re: Apparently a Puppet Hiera error message points to a 404 In PUP-6358 it is clearly stated that we should have used a URL without the ".z" part. We should naturally fix this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7360) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7360 Apparently a Puppet Hiera error message points to a 404 Change By: Henrik Lindberg Assignee: Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7391) Fix problem with "Attempt to redefine entity" when using type aliases as class parameter
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7391 Fix problem with "Attempt to redefine entity" when using type aliases as class parameter Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7360) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7360 Apparently a Puppet Hiera error message points to a 404 Change By: Henrik Lindberg Fix Version/s: PUP 4.10.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2849) correct deprecation warning around export tool
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2849 correct deprecation warning around export tool Change By: Russell Mull Sprint: PuppetDB 2017-04-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3381) (maint) don't duplicate CTE for inactive nodes
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3381 (maint) don't duplicate CTE for inactive nodes Change By: Russell Mull Sprint: PuppetDB 2017-04-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3379) (maint) allow paging options to be specified in two places
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3379 (maint) allow paging options to be specified in two places Change By: Russell Mull Sprint: PuppetDB 2017-04-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3378) (maint) Better indexing for package_inventory related queries
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3378 (maint) Better indexing for package_inventory related queries Change By: Russell Mull Sprint: PuppetDB 2017-04-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3378) (maint) Better indexing for package_inventory related queries
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3378 (maint) Better indexing for package_inventory related queries Change By: Russell Mull Story Points: 1 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7396) hiera function deprecation errors generate invalid docs urls
Title: Message Title Henrik Lindberg commented on PUP-7396 Re: hiera function deprecation errors generate invalid docs urls This can be fixed on the docs site, thereby also fixing this for versions already released. Ping Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4183) File Resource should be able to handle a UNC on Windows
Title: Message Title Josh Cooper commented on PUP-4183 Re: File Resource should be able to handle a UNC on Windows Jorie Tappa Assigning this to you as the latest docs need updating to say that file sources can be UNC paths. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7397) FileBucket should use `Puppet::Util::replace_file` to write contents
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7397 FileBucket should use `Puppet::Util::replace_file` to write contents Change By: Moses Mendoza Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7397) FileBucket should use `Puppet::Util::replace_file` to write contents
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7397 FileBucket should use `Puppet::Util::replace_file` to write contents Issue Type: Bug Assignee: Unassigned Created: 2017/03/23 2:44 PM Priority: Normal Reporter: Moses Mendoza Per feedback on PR for PUP-1334, https://github.com/puppetlabs/puppet/pull/5704, it would be ideal to use Puppet::Util::replace_file to write the contents file instead of Puppet::FileSystem::open. Due to PUP-7394 and PUP-7395 doing so at the time of filing this ticket was not optimal, but once those are addressed this change should be made. See https://github.com/MosesMendoza/puppet/commit/9f1bf4b3a186942439f41a282c57823bae4af5a2 for an implementation Add Comment
Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Ethan Brown commented on PUP-1334 Re: Empty clientbucket files produce errors Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/57a26e9501a466f7e76c6c675eb0f4b13a7162fc Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4183) File Resource should be able to handle a UNC on Windows
Title: Message Title Josh Cooper assigned an issue to Jorie Tappa Puppet / PUP-4183 File Resource should be able to handle a UNC on Windows Change By: Josh Cooper Assignee: Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7396) hiera function deprecation errors generate invalid docs urls
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-7396 hiera function deprecation errors generate invalid docs urls Change By: Eric Sorenson Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7396) hiera function deprecation errors generate invalid docs urls
Title: Message Title
Eric Sorenson created an issue
Puppet / PUP-7396
hiera function deprecation errors generate invalid docs urls
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/03/23 2:23 PM
Priority:
Normal
Reporter:
Eric Sorenson
The errors emitted from using the now-deprecated hiera_* functions generate deprecation messages that point to non-existent URLs on the docs site. They interpolate Puppet.version into the URL string, but the docs are not versioned to X.Y.Z releases, only X.Y.
[eric@cipater.local ~/Sandbox/puppet/lib/puppet]% ag 'docs.puppet.*Puppet.version'
parser/functions/hiera.rb
81:See https://docs.puppet.com/puppet/#{Puppet.version}/reference/deprecated_language.html.
Jira (PUP-7395) Puppet::Util.replace_file ignores mode parameter when file exists
Title: Message Title Ethan Brown created an issue Puppet / PUP-7395 Puppet::Util.replace_file ignores mode parameter when file exists Issue Type: Improvement Assignee: Unassigned Created: 2017/03/23 2:20 PM Priority: Normal Reporter: Ethan Brown Documentation for replace_file very explicitly states: # As far as possible the state of the existing file, such as mode, is # preserved. This works hard to avoid loss of any metadata, but will result # in an inode change for the file. It seems a bit peculiar to pass a mode value into the API and have it ignored - so I think the order of precedent here seems incorrect. It's also possible I've misunderstood all the use
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Joshua Keiser updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Joshua Keiser Fix Version/s: PUP 4.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7394) Puppet::Util.replace_file cannot be used to create a read-only file (on non-Windows)
Title: Message Title
Ethan Brown created an issue
Puppet / PUP-7394
Puppet::Util.replace_file cannot be used to create a read-only file (on non-Windows)
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/03/23 2:09 PM
Priority:
Normal
Reporter:
Ethan Brown
Assuming a file does not yet exist, a call to FileUtils.replace_file like the following will fail:
Puppet::Util.replace_file('/tmp/foo', 0440) { |of| FileUtils.copy_stream(StringIO.new("\u1234"), of) }
With an error like:
Errno::EACCES: Permission denied @ rb_sysopen - /tmp/foo20170323-24678-rg0fn9
from
Jira (PUP-7364) Parser result no longer contains current method
Title: Message Title Henrik Lindberg commented on PUP-7364 Re: Parser result no longer contains current method Ping Thomas Hallgren, you made a fix to ensure Puppet Strings worked - that was a similar issue IIRC. Was that for the model method. Corey Osman the current method changed name to model at some point in the past - and we may have fixed this already for model. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3381) (maint) don't duplicate CTE for inactive nodes
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3381 (maint) don't duplicate CTE for inactive nodes Issue Type: Bug Assignee: Unassigned Created: 2017/03/23 1:52 PM Priority: Normal Reporter: gepetto-bot Only apply the CTE to non-subqueries. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7237) fix puppet acceptance Rake tasks
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7237 fix puppet acceptance Rake tasks Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7372) puppet 4.9.4 lookup fails with undefined method error message
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7372 puppet 4.9.4 lookup fails with undefined method error message Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7328) Duplication errors on Puppet Class "settings".
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7328 Duplication errors on Puppet Class "settings". Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7370) Ensure that returned value from data provider is type checked only once.
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7370 Ensure that returned value from data provider is type checked only once. Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7371) Type mismatches for variants with undef are incorrectly reported
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7371 Type mismatches for variants with undef are incorrectly reported Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7334 add a default hierarchy to module hiera.yaml Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7281) Add support for default options in hiera.yaml v 5
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7281 Add support for default options in hiera.yaml v 5 Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7330) Puppet::LookupKey and Puppet::LookupValue types are unavailable to Hiera backend functions
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7330 Puppet::LookupKey and Puppet::LookupValue types are unavailable to Hiera backend functions Change By: William Hopper Status: Ready for CI Test Assignee: Josh Cooper qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3380) Puppet DB Dashboard Flatlines
Title: Message Title Rob Lucke created an issue PuppetDB / PDB-3380 Puppet DB Dashboard Flatlines Issue Type: Bug Affects Versions: PDB 4.3.2 Assignee: Unassigned Attachments: PDB-Screen-12.22-Before.png, PDB-Screen-12.44-After.png Components: PuppetDB Created: 2017/03/23 12:54 PM Environment: PE 2017.1 Priority: Normal Reporter: Rob Lucke Displaying data from the PDB dashboard is great! After displaying data long enough to fill the width of the display boxes on the page (one hour?), leaving the page for the display width's worth of time will result in flat lines being displayed, even with continuing activity
Jira (PUP-7393) AIX Provider acts strange with user resource
Title: Message Title Eric Anderson created an issue Puppet / PUP-7393 AIX Provider acts strange with user resource Issue Type: Bug Assignee: Unassigned Components: Modules Created: 2017/03/23 12:44 PM Environment: When a user is in a group on a Linux server and a user resource is created for that user, if new groups are specified in the resource, the user is moved out of his previous groups into the groups specified. In AIX the user stays in his old groups and gets added to his new groups. The AIX functionality should mimic the Linux functionality. Priority: Normal Reporter: Eric Anderson Add Comment
Jira (PUP-7143) CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
Title: Message Title Kenn Hussey commented on PUP-7143 Re: CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR Stan Duffy ping. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Kenn Hussey commented on PUP-1334 Re: Empty clientbucket files produce errors Moses Mendoza +1, thanks for the heads up. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7365) Make puppet agent and puppet server first check for a clock skew
Title: Message Title Eric Sorenson commented on PUP-7365 Re: Make puppet agent and puppet server first check for a clock skew I'm going to close this as won't-fix because we used to do this and removed it because it was misleading - it's very, very hard to programmatically determine the clock situation. err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often because the time is out of sync on the server or client Led to lots of confusion like this: err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often because the time is out of sync on the server or client https://groups.google.com/d/topic/puppet-users/wKFMlPNAFZ0/discussion Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-7392) Acceptance: Create test verifying that stopping the puppet service on Windows does
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7392 Acceptance: Create test verifying that stopping the puppet service on Windows does Change By: Kurt Wall QA Risk Assessment Reason: Test ricket ticket Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3379) (maint) allow paging options to be specified in two places
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3379 (maint) allow paging options to be specified in two places Issue Type: Bug Assignee: Unassigned Created: 2017/03/23 11:32 AM Priority: Normal Reporter: gepetto-bot Previously paging options supplied in a query would cause paging options supplied outside the query to be ignored. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7392) Acceptance: Create test verifying that stopping the puppet service on Windows does
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7392 Acceptance: Create test verifying that stopping the puppet service on Windows does Change By: Kurt Wall QA Risk Assessment Reason: Test ricket Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7392) Acceptance: Create test verifying that stopping the puppet service on Windows does
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7392 Acceptance: Create test verifying that stopping the puppet service on Windows does Change By: Kurt Wall QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7392) Acceptance: Create test verifying that stopping the puppet service on Windows does
Title: Message Title Kurt Wall created an issue Puppet / PUP-7392 Acceptance: Create test verifying that stopping the puppet service on Windows does Issue Type: Bug Affects Versions: PUP 4.10.z Assignee: Kurt Wall Components: Windows Created: 2017/03/23 11:32 AM Priority: Normal Reporter: Kurt Wall PUP-2987 fixed a set of corner cases in the puppet service on Windows in which the service would hang instead of stopping. This ticket tracks creating an acceptance test to verify this behavior. Add Comment
Jira (PUP-7386) (possibly) Broken FileBucket Write Atomicity under Puppet Server
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7386 (possibly) Broken FileBucket Write Atomicity under Puppet Server Change By: Moses Mendoza Summary: (possibly) Broken FileBucket Write Atomicity under Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7299) Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX
Title: Message Title Susan McNerney updated an issue Puppet / PUP-7299 Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX Change By: Susan McNerney Labels: davis-triage lts-backport-request Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1334 Empty clientbucket files produce errors Change By: Moses Mendoza Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7364) Parser result no longer contains current method
Title: Message Title Josh Cooper commented on PUP-7364 Re: Parser result no longer contains current method ping Henrik Lindberg looks language related Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1592) Networking key/value pair for Interface Speed and Duplex State
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1592 Networking key/value pair for Interface Speed and Duplex State Change By: Geoff Nichols Labels: puppethack Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7390) Prefer minitar gem to `tar` command when available
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7390 Prefer minitar gem to `tar` command when available Change By: Geoff Nichols Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7390) Prefer minitar gem to `tar` command when available
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7390 Prefer minitar gem to `tar` command when available Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7383) Puppet with openssl 1.1 fails
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7383 Puppet with openssl 1.1 fails Change By: Geoff Nichols Labels: needs_epic Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7383) Puppet with openssl 1.1 fails
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7383 Puppet with openssl 1.1 fails Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7383) Puppet with openssl 1.1 fails
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7383 Puppet with openssl 1.1 fails Change By: Geoff Nichols Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7375) Puppet does not change file to directory when selinux is enabled
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7375 Puppet does not change file to directory when selinux is enabled Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7375) Puppet does not change file to directory when selinux is enabled
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7375 Puppet does not change file to directory when selinux is enabled Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7375) Puppet does not change file to directory when selinux is enabled
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7375 Puppet does not change file to directory when selinux is enabled Change By: Geoff Nichols Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7365) Make puppet agent and puppet server first check for a clock skew
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7365 Make puppet agent and puppet server first check for a clock skew Change By: Geoff Nichols Sprint: Agent Triage Needs Information Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7343) exec path and environment attributes do not work as documented
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7343 exec path and environment attributes do not work as documented Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5008) Add support for the user type's forcelocal attribute on Solaris
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5008 Add support for the user type's forcelocal attribute on Solaris Change By: Geoff Nichols Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5008) Add support for the user type's forcelocal attribute on Solaris
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5008 Add support for the user type's forcelocal attribute on Solaris Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2987) Puppet service hangs when attempting to stop on Windows
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2987 Puppet service hangs when attempting to stop on Windows Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2987) Puppet service hangs when attempting to stop on Windows
Title: Message Title Kurt Wall commented on PUP-2987 Re: Puppet service hangs when attempting to stop on Windows Ethan Brown To test this with a beaker test, would it be sufficient to adopt Josh Cooper's method: this the following sequence of commands some number of times, verifying that the stop, start, and query options succeed each time (no hang, obviously, but also no warning/error) and make appropriate entries in the log? sc stop puppet sc query puppet sc start puppet sc query puppet Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1585) Facter can't resolve metadata on google cloud instances
Title: Message Title Branan Riley commented on FACT-1585 Re: Facter can't resolve metadata on google cloud instances Cherry-picked to stable as cd5d2eccdf052b966eaf18d0f6a4faeb15a752af Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6854) OSX: Warning output when using puppet resource service
Title: Message Title Samuel Keeley commented on PUP-6854 Re: OSX: Warning output when using puppet resource service Pull request https://github.com/puppetlabs/puppet/pull/5730 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7389) puppet-client-tools RPM is signed with a revoked GPG key
Title: Message Title Trevor Vaughan commented on PUP-7389 Re: puppet-client-tools RPM is signed with a revoked GPG key Morgan Rhodes Could we get the existing packages re-signed? Presently, it doesn't play well with systems that require signed package validation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7380) Acceptance: Cisco eXR 6.1.3 VM fails to run augeus test successfully
Title: Message Title Kurt Wall assigned an issue to qa Puppet / PUP-7380 Acceptance: Cisco eXR 6.1.3 VM fails to run augeus test successfully Change By: Kurt Wall Status: Ready for CI Test Assignee: Stan Duffy qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-3107 new-command-schema validation prevents PDB/NewRelic integration Change By: Susan McNerney Labels: davis-triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Susan McNerney commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration Approved for inclusion in 4.2.3.2 & by extension the 2016.4.4 LTS release by the Davis leads. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3378) (maint) Better indexing for package_inventory related queries
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3378 (maint) Better indexing for package_inventory related queries Issue Type: Bug Assignee: Unassigned Created: 2017/03/23 9:52 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-3364) Replace Rust client with golang client
Title: Message Title Michael Stahnke commented on PDB-3364 Re: Replace Rust client with golang client Ruby isn't usable for client tools because we don't ship ruby for Mac OS X or WIndows, which are the two major platforms for client tools. Discussion has been primarily in response to selecting golang for transparent container work and buddha. You can see the discussion for budda https://docs.google.com/document/d/1OFEOeD64ZqsgVnLAUAJRaViE2et7ra7zIOxtJrvWlvc/edit?ts=58b5dfab and TC https://groups.google.com/a/puppet.com/forum/#!topic/discuss-tech/dzQcXdqTcpo The discussion since then has been that since: 1. We don't have a giant investment in rust 2. We're going to introduce golang We should reduce our technical footprint by backing away from Rust in favor of golang for the tools where Rust had previously been selected. Deepak Giridharagopal can probably give more technical direction here, we were talking and he asked me to ticket out the work. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1585) Facter can't resolve metadata on google cloud instances
Title: Message Title Eric Delaney updated an issue Facter / FACT-1585 Facter can't resolve metadata on google cloud instances Change By: Eric Delaney QA Risk Assessment Reason: We should try to automate testing this QA Risk Assessment: Needs Assessment Automate QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings
Title: Message Title Kenn Hussey commented on PUP-1890 Re: URI.unescape mangles UTF-8 paths producing invalid ASCII strings Ethan Brown thanks, that's fine, just thought I would double-check since it was in progress. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7391) Fix problem with "Attempt to redefine entity" when using type aliases as class parameter
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7391 Fix problem with "Attempt to redefine entity" when using type aliases as class parameter Issue Type: Bug Assignee: Thomas Hallgren Created: 2017/03/23 7:16 AM Fix Versions: PUP 4.10.z Priority: Normal Reporter: Thomas Hallgren If a function parameter declaration or return type, references a type that has not yet been loaded, and that type is prefixed with the name of a module that has not yet been loaded, then the loaders will first make an attempt to load the files in the modules manifests directory. If such a file, in turn, also references the same type, then that triggers a recursive load. When the recursive call returns, the loader will still try to add the type, which results in an "Attempt to redefine entity" error. Add Comment
Jira (PUP-7335) "user" resource changes root role to root user on Solaris 11 during root password change
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7335 "user" resource changes root role to root user on Solaris 11 during root password change Change By: Geoff Nichols Sprint: Agent Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Thomas Hallgren commented on PUP-7333 Re: make it possible to control partial ordering of layers So, the terminology for "level" is different if you call next_level_lookup and use "next_level" here? That doesn't make sense to me. The temr "next_layer", as I wrote before, suggests a layer, not the layers below that layer. I'm trying to find a term that describes all layers below this layer, both in the hierarchy and in the proposed context function. It should be the same term. I think the best so-far is "below". I don't quite buy that it would be perceived as pointing to the next declaration in the same file as that makes no sense at all. Why then add it in the first place? The same is true for the term "next_level". I think users will understand that it's not a noop. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Henrik Lindberg commented on PUP-7333 Re: make it possible to control partial ordering of layers did you mean "next_layer"? (next_level would be a noop, it is the level below this in the same hierarchy). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Thomas Hallgren commented on PUP-7333 Re: make it possible to control partial ordering of layers If "lookup_below" is changed to "next_level_lookup", then I would suggest the keyword here to be "next_level". It's part of a definition so I don't thing it needs to be prefixed with a verb. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Henrik Lindberg commented on PUP-7333 Re: make it possible to control partial ordering of layers "perform lookup below this layer here instead of at the end" yes, agree. Consider that "lookup below" is changed to "next_level_lookup", which makes the concept of "below" free to mean "layer below". I do however associate the word "below" with the actual text in the file in question as you often read "see below", so I don't know if "below" is the best term for either concept. Trying to come up with a single household word, but end up with names like go_down, include_next, process_next, search_next, include_lower_layers, search_lower_layers, drill_down. Of those search_lower_layers is quite descriptive. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Thomas Hallgren commented on PUP-7333 Re: make it possible to control partial ordering of layers The difference is that next_layer just suggests a layer, not what's below that layer in turn (which I think it should). I would like this to have the functional meaning "perform lookup below this layer here instead of at the end" so that the logic could trigger on this and prevent further lookups once the current layer is done. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Henrik Lindberg commented on PUP-7333 Re: make it possible to control partial ordering of layers ok, the only reason I used two words was to have that entry be like the others and that you could name your "yield" so to say. That is not required at all and you would probably struggle to say something meaningful in its name anyway. So, I like your proposal to just have a keyword instead of name, etc. Suggest we use next_layer as the keyword. I don't think the concept of "yield" works for the people that work with data and hierarchies. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Henrik Lindberg commented on PUP-7333 Re: make it possible to control partial ordering of layers There is no need (it should be an error) to specify layer: modules in a global hiera.yaml. If we want to make the concepts related and to also reinforce the terminology, we could use next: layer (i.e. env in global, and modules in an env). And change the name of context.lookup_below in PUP-7332 to context.next_level_lookup - i.e. they are both about "next-ness", one about "layer" and one about "level". Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Thomas Hallgren commented on PUP-7333 Re: make it possible to control partial ordering of layers Thinking one step ahead. The hierarchy is an array of hashes. Each hash as a name, a function, etc. Here, we could replace the whole hash with a simple keyword such as "yield" or "yield_below". There's no point in having name. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7333) make it possible to control partial ordering of layers
Title: Message Title Thomas Hallgren commented on PUP-7333 Re: make it possible to control partial ordering of layers What I'm after in PUP-7332 is consistency. The term "below" must have the same meaning in all cases. As you point out, it cannot when used together with the term "layer" and still give the same meaning as in lookup_below, so introducing that here would actually make things worse. Some other terminology must be used altogether, like "yield: below" instead of "layer: ". What I wonder is, when is there ever a need to state 'layer: module' in the global layer? The only time I can think of, is when you actually want to accomplish a "below" in the sense that it has in lookup_below. The global layer must then have two entries, one using "layer: environment" and another using "layer: module". I'm not so sure it's a good thing to introduce a mechanism that will allow you to bypass the environment or reverse the priority of the environment and module layer. I mean, it's OK for a layer to state, "I yield to the things below me" but it's not OK to start messing with how those things are organized internally. Not to mention the mess it will create in the current implementation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
